Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/fockus/skill-memory-bankWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/fockus/skill-memory-bank/done)<a href="https://agentmods.dev/commands/fockus/skill-memory-bank/done"><img src="https://agentmods.dev/badge/commands/fockus/skill-memory-bank/done/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/fockus/skill-memory-bank/done"><img src="https://agentmods.dev/badge/commands/fockus/skill-memory-bank/done.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00040 | $0.02068 |
| Opus 5.5 | $0.00016 | $0.00827 |
| Sonnet 5.5 | $0.00008 | $0.00414 |
| Haiku 4.5 | $0.00004 | $0.00207 |
Grade A, and why
done scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Canonical session-end command. /mb done is an alias that dispatches here.
Storage note. Resolve the active bank path through
mb_resolve_path(inscripts/_lib.sh). Bank may be local (./.memory-bank/), global (<agent_config>/memory-bank/projects/<id>/.memory-bank/, registered via--storage=global), or legacy (.claude-workspace). Allmb-*scripts called below already respect the resolver — pass--mb <resolved-path>when needed. If[MEMORY BANK: ABSENT], this command is a no-op except for surfacing the absent state.
Set SKILL_DIR to the absolute directory containing the loaded SKILL.md (or use MB_SKILLS_ROOT), and MB_AGENT to the current host id for global registry lookup. Keep cwd at the project. Include this setup in the same shell invocation as each command below.
SKILL_DIR="${MB_SKILLS_ROOT:-${SKILL_DIR:?Set SKILL_DIR from the loaded skill path}}"
source "$SKILL_DIR/scripts/_lib.sh"
BANK="$(mb_resolve_path)"
if [ ! -d "$BANK" ]; then
echo "[MEMORY BANK: ABSENT]"
exit 0
fi
BANK="$(cd "$BANK" && pwd -P)"
export MB_PATH="$BANK"
0. Mandatory done-gates (runs even without a plan)
Run the gate set first — these are mandatory whether or not a plan was active:
bash "$SKILL_DIR/scripts/mb-done-gates.sh" --mb "$BANK" --dir "$PWD"
It runs three independent checks in sequence (each emits a structured JSON line):
- Tests — dispatches the test runner (scope=touched if a baseline commit is inferable, else scope=full).
not_applicable(no stack detected) counts as PASS with a logged WARN. - Rules (deterministic) —
scripts/mb-rules-check.shon the working tree; a CRITICAL violation fails the gate. - Placeholders —
scripts/mb-rules-check.sh --placeholders-onlyscans staged + uncommitted source forTODO|FIXME|XXX|...|pseudocode; any hit fails the gate. The deny list is configurable viapipeline.yaml:done_placeholders.deny.
Exit semantics: exit 0 only when every required gate passes. On any failure the script exits 2 and /mb done must stop — do not close the session.
Force override — bash "$SKILL_DIR/scripts/mb-done-gates.sh" --mb "$BANK" --dir "$PWD" --force --reason "<one-line>":
--reasonis mandatory when forcing; the script refuses--forcewithout it (non-zero exit, no mutation).- On a forced run with failures the script appends
### NOTE: /mb done --force — gates failed: <gates>: <reason>toprogress.mdunder today's## YYYY-MM-DDheading (creating the heading if absent), writes the failure detail to<bank>/tmp/done-gate-failure-<ts>.json, then exits0so the close can proceed on the record. - Config lives in
pipeline.yaml:done_gates(enabled,required,allow_force). Whenallow_force: false,--forceis rejected outright.
If gates pass (or are forced), continue with the rest of this flow.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago Changed · +24 tokens per session 5f21a28ebdea
- 1mo ago Changed · +15 lines 021added8a41
- 1mo ago Changed · +1 lines 80f0581e89f2
- 1mo ago First seen · 74 lines · 16 tokens per session scan A c81f91e0fab6
done is a command published in the GitHub repository fockus/skill-memory-bank (28 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 2,068 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
unity-session-save
Save the current session state as a labeled snapshot to .claude/state/sessions/ .json for later /unity-session-resume.
overview
Automatically coordinate, format, and learn from Claude Code operations using hooks with MCP tool integration.
session-memory
Maintain context and learnings across Claude Code sessions for continuous improvement.
session-end
Cleanup and persist session state before ending work.
memory-manager
Knowledge management with Memory tools for persistent insights.
hive-mind-memory
Command documentation for hive-mind-memory in category hive-mind.