Neat-Freak Knowledge Closeout
KKKKhazix/khazix-skills
Brings project docs, agent rule files, authorized memory and leftover workspace files back in line with what the code and runtime actually do at the end of a work session.
Create and maintain one committed per-project memory file (PROJECT.md) so agents stop re-discovering the same facts every cold session.
Install Honey Memory
$ npx skills add Green-PT/honey-for-devs --skill honey-memory -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Green-PT/honey-for-devs honey-memory --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Green-PT/honey-for-devs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/honey-memory .claude/skills/honey-memory && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "honey-memory" agent skill from https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-memory into .claude/skills/honey-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honey-memory", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-memoryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Green-PT/honey-for-devs --skill honey-memory -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Green-PT/honey-for-devs honey-memory --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Green-PT/honey-for-devs.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/honey-memory .agents/skills/honey-memory && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "honey-memory" agent skill from https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-memory into .agents/skills/honey-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honey-memory", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Green-PT/honey-for-devs --skill honey-memory -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Green-PT/honey-for-devs honey-memory --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Green-PT/honey-for-devs.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/honey-memory .cursor/skills/honey-memory && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "honey-memory" agent skill from https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-memory into .cursor/skills/honey-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honey-memory", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Green-PT/honey-for-devs.git --path skills/honey-memory--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Green-PT/honey-for-devs --skill honey-memory -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Green-PT/honey-for-devs honey-memory --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Green-PT/honey-for-devs.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/honey-memory .gemini/skills/honey-memory && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "honey-memory" agent skill from https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-memory into .gemini/skills/honey-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honey-memory", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Green-PT/honey-for-devs honey-memoryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Green-PT/honey-for-devs --skill honey-memory -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Green-PT/honey-for-devs.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/honey-memory .github/skills/honey-memory && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "honey-memory" agent skill from https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-memory into .github/skills/honey-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honey-memory", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Green-PT/honey-for-devs --skill honey-memory -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Green-PT/honey-for-devs honey-memory --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Green-PT/honey-for-devs.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/honey-memory .opencode/skills/honey-memory && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "honey-memory" agent skill from https://github.com/Green-PT/honey-for-devs/tree/main/skills/honey-memory into .opencode/skills/honey-memory/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "honey-memory", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
honey-memory- GitHub stars
- 313
- Token cost
- ~950 tokens
- SKILL.md length
- 478 words
- Files
- 1
- Skills in repo
- 14
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create and maintain one committed per-project memory file (PROJECT.md) so agents stop re-discovering the same facts every cold session.
- Works in 4 steps: One file per repo: PROJECT.md at the… → Back up before overwriting an existing… → Write only three kinds of fact (derive… → …
- Asked to set up project memory/context
- SKILL.md covers Scaffold (create), Never store, Update and One file vs many, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Honey Memory is an agent skill from Green-PT/honey-for-devs. Create and maintain one committed per-project memory file (PROJECT.md) so agents stop re-discovering the same facts every cold session. Stores only the stable, expensive-to-rediscover, not-in-the-code context — architecture + why, build/test/run commands, decisions and dead-ends — as human-readable markdown, versioned with the code so it can't silently rot. Use when asked to set up project memory/context, stop agents re-grepping the codebase, scaffold or refresh a PROJECT.md / CLAUDE.md memory section, or cut…
Its SKILL.md is about 950 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows, covering Agent memory and Agent instruction files. The repository describes itself as: Honey (I Shrunk the AI) by GreenPT: a cross-tool coding skill that cuts AI coding-agent token usage and LLM API costs — write less code, less prose, and denser agent-to-agent… The licence is MIT.
When your agent uses it
- Asked to set up project memory/context
- Stop agents re-grepping the codebase
- Refresh a PROJECT.md / CLAUDE.md memory section
- Cut cold-start rediscovery cost
Example prompts
- “/honey-memory”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- One file per repo: PROJECT.md at the root, committed (not ~/.claude).
- Back up before overwriting an existing file: copy → FILE.original.md.
- Write only three kinds of fact (derive by reading the repo)
- Report what was written and the file path.
What it can do on your machine
Read from SKILL.md and the folder at commit 9169fc5. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Honey Memory loads about 950 tokens when it runs. Until then it costs about 152 tokens; SKILL.md has 478 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Green-PT/honey-for-devs at commit 9169fc5, republished under its MIT licence (© Green-PT). 478 words, ~950 tokens.
Download SKILL.mdSave it as
.claude/skills/honey-memory/SKILL.md (or your agent's skills folder).- name
- honey-memory
- description
- Create and maintain one committed per-project memory file (PROJECT.md) so agents stop re-discovering the same facts every cold session. Stores only the stable, expensive-to-rediscover, not-in-the-code context — architecture + why, build/test/run commands, decisions and dead-ends — as human-readable markdown, versioned with the code so it can't silently rot. Use when asked to set up project memory/context, stop agents re-grepping the codebase, scaffold or refresh a PROJECT.md / CLAUDE.md memory section, or cut cold-start rediscovery cost. Prose context only — never code, config, or data.
- license
- MIT
Honey Memory
Lever 2 applied to discovery cost. Every cold session re-greps the same things — where auth lives, the build command, why X is shaped Y. One committed file replaces N rediscovery round-trips with a single cached read, on every future session. The cheapest token is the one not re-derived.
The win is per-session and recurring. The risk is staleness — a wrong cached fact costs more than no file. So the file lives in git, next to the code that can invalidate it, and is fixed in the same change that breaks it.
Scaffold (create)
- One file per repo:
PROJECT.mdat the root, committed (not~/.claude). If the repo already hasCLAUDE.md/AGENTS.md, add/refresh a## Memorysection there instead — don't add a second file. - Back up before overwriting an existing file: copy →
FILE.original.md. If that backup already exists, stop and ask. Never clobber a restore point. - Write only three kinds of fact (derive by reading the repo):
- Architecture + conventions an agent can't cheaply grep — where things live, and why (the intent, not the file list).
- Build / test / run commands, env, and gotchas.
- Decisions and dead-ends — choices made, paths tried and rejected. This is intent; it is never in the code.
- Report what was written and the file path.
Never store
- Anything derivable from source — code structure, symbol locations, past fixes, git history. Re-deriving is cheaper than maintaining, and never stale.
- Secrets, tokens, credentials. The file is committed.
- Transient state — open TODOs, this-week status. That rots fastest.
If a fact is stable + expensive-to-rediscover + not-in-the-code, write it. Everything else, let agents derive on demand — caching it is where these systems quietly lose money.
Show full SKILL.md (204 more words)Show less
Update
A markdown file does not update itself. Reliability = discipline, not infra:
- Same-change rule (primary). When code changes invalidate a fact, fix the fact in the same commit. Review catches drift because the file is in git.
- On-demand refresh. Re-read the repo and rewrite stale entries; show the diff. Don't blind-append — appending is how these files bloat and rot.
- Treat a fact as superseded, not accumulated: replace the old line, don't stack a new one beside it.
One file vs many
Start with one file. Split only when it crosses ~150–200 lines or covers clearly separable domains — then go to a thin index + topic files loaded on demand. Below that, an index costs more (the always-loaded tax) than it saves.
Keep terse
Apply Honey Lever 2 to the content — fragments over paragraphs, no narration of what the code already says. A bloated memory file is a per-session input tax. Keep it human-readable markdown: you (and reviewers) hand-edit it, so don't use a wire format — staleness costs more than the tokens a dense format would save.
Boundaries
Reversible — FILE.original.md is the restore path when overwriting. Verify
every written fact against the current code before reporting done; an unverified
fact is worse than an absent one.
© Green-PT, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/honey-memory of Green-PT/honey-for-devs.
Open the folder on GitHubat commit 9169fc5
Compare with similar skills
Honey Memory next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Honey Memory this skillGreen-PT/honey-for-devs | 313 | — | ~950 | Automated safety check: Pass | MIT | |
| Neat-Freak Knowledge CloseoutKKKKhazix/khazix-skills | 21k | — | ~1.9k | Automated safety check: Pass | MIT | |
| SkillOpt Sleep Cyclemicrosoft/SkillOpt | 18k | — | ~2.3k | Automated safety check: Pass | MIT | |
| CLAUDE.md Improveranthropics/claude-plugins-official | 38k | 5 repos | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Harness Engineering10xChengTu/harness-engineering | 102 | 1 repos | ~1k | Automated safety check: Pass | None | |
| Codebase Analyzerseverity1/claude-code-auto-memory | 159 | — | ~1.5k | Automated safety check: Pass | MIT |
Similar skills
- Official
SkillOpt Sleep Cycle
microsoft/SkillOpt
Runs an on-demand or nightly sleep cycle that reviews past Claude Code sessions and proposes validated updates to CLAUDE.md and skills.
- Official
CLAUDE.md Improver
anthropics/claude-plugins-official
Finds every CLAUDE.md file in a repository, scores each against quality criteria, shows a report, then makes targeted updates after you approve.
Harness Engineering
10xChengTu/harness-engineering
Set up and improve harness engineering (AGENTS.md, docs/, lint rules, eval systems, project-level prompt engineering) for AI-agent-friendly codebases.
Codebase Analyzer
severity1/claude-code-auto-memory
This skill should be used when the user asks to "initialize auto-memory", "create CLAUDE.md", "set up project memory", or runs the /auto-memory:init command.
Self Improving For Codex
GODGOD126/self-improving-for-codex
Build or maintain a Codex-native self-improving memory loop using global AGENTS.md, a persistent memories directory, and optional nightly refinement automation.
More from Green-PT/honey-for-devs
All 14 skills in this repoHoney
Green-PT/honey-for-devs
Write less code and say less about it. An agent skill from Green-PT/honey-for-devs.
Honey Ccr
Green-PT/honey-for-devs
Compress-Cache-Retrieve for huge, repetitive array tool output (logs, scan results, time series, event streams) before it enters context.
Honey Eco
Green-PT/honey-for-devs
Report this session's output tokens and CO₂ by running the repo's committed EcoLogits port, plus the modelled CO₂/$ saved vs a no-Honey baseline — always labelled with the bench stamp it came from.
Honey Gain
Green-PT/honey-for-devs
Show Honey's benchmark scoreboard — the committed quality and token results per task tier (code, user-facing, agent-to-agent) from bench/.
Honey Px
Green-PT/honey-for-devs
Read huge, dense, read-only text as rendered PNG pages instead of raw text — image tokens scale with pixels, not characters, so token-dense bulk (big files, vendored code, diffs, logs) costs ~60–75%…
Honey Superpowers
Green-PT/honey-for-devs
Stack Honey onto Superpowers-style workflows (subagent-driven-development, dispatching-parallel-agents, executing-plans) and any orchestration that dispatches fresh subagents.
Related
Categories
Questions about Honey Memory
What does Honey Memory do?
Create and maintain one committed per-project memory file (PROJECT.md) so agents stop re-discovering the same facts every cold session. Honey Memory is an agent skill from Green-PT/honey-for-devs.md) so agents stop re-discovering the same facts every cold session.
When should I use Honey Memory?
Honey Memory fits situations like: asked to set up project memory/context; stop agents re-grepping the codebase; refresh a PROJECT.md / CLAUDE.md memory section; cut cold-start rediscovery cost.
How do I install Honey Memory in Claude Code?
Run `npx skills add Green-PT/honey-for-devs --skill honey-memory -a claude-code`. Or copy the skill folder (skills/honey-memory in Green-PT/honey-for-devs) into .claude/skills/honey-memory in your project. Claude Code loads it when a task matches its description.
How do I install Honey Memory in Codex?
Run `npx skills add Green-PT/honey-for-devs --skill honey-memory -a codex`. Or copy the skill folder (skills/honey-memory in Green-PT/honey-for-devs) into .agents/skills/honey-memory in your project. Codex loads it when a task matches its description.
Can I use Honey Memory in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Green-PT/honey-for-devs --skill honey-memory -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/honey-memory, .gemini/skills/honey-memory, .github/skills/honey-memory and .opencode/skills/honey-memory in your project.
What does Honey Memory need to run?
SKILL.md names no scripts, command-line tools or credentials: Honey Memory is instructions for the agent only.
Does Honey Memory access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Honey Memory safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Honey Memory use?
Honey Memory is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Honey Memory use?
About 950 tokens (SKILL.md is roughly 3.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Honey Memory?
Skills that share tags, products or a category with Honey Memory: Neat-Freak Knowledge Closeout (KKKKhazix/khazix-skills, 21k stars), SkillOpt Sleep Cycle (microsoft/SkillOpt, 18k stars), CLAUDE.md Improver (anthropics/claude-plugins-official, 38k stars) and Harness Engineering (10xChengTu/harness-engineering, 102 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Honey Memory?
Green-PT (a GitHub organization) maintains it in Green-PT/honey-for-devs, which has 313 GitHub stars. The repository holds 14 skills in this directory. The repository was last updated on September 7, 2026.
Source: Green-PT/honey-for-devs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.