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/plan)<a href="https://agentmods.dev/commands/fockus/skill-memory-bank/plan"><img src="https://agentmods.dev/badge/commands/fockus/skill-memory-bank/plan/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/plan"><img src="https://agentmods.dev/badge/commands/fockus/skill-memory-bank/plan.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.00038 | $0.02578 |
| Opus 5.5 | $0.00015 | $0.01031 |
| Sonnet 5.5 | $0.00008 | $0.00516 |
| Haiku 4.5 | $0.00004 | $0.00258 |
Grade A, and why
plan 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 2d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan: $ARGUMENTS
Canonical planning command. /mb plan is an alias that dispatches here.
Storage note. Resolve the active bank path through
mb_resolve_path(inscripts/_lib.sh). The plan file ends up at<resolved-bank>/plans/<YYYY-MM-DD>_<type>_<topic>.mdregardless of whether the bank is local, registered global storage, or legacy.claude-workspace. If[MEMORY BANK: ABSENT](rules-only mode), refuse to plan and tell the user to run/mb initfirst — but do not auto-initialize.
Skill bundle root
Every bundled helper below runs through the skill bundle root, never a bare scripts/… path (the
working directory is the user's project, where scripts/ is absent or belongs to someone else):
SKILL_DIR="${MB_SKILLS_ROOT:-${SKILL_DIR:-$HOME/.claude/skills/memory-bank}}"
[ -f "$SKILL_DIR/scripts/_lib.sh" ] || { echo "mb: skill bundle not found at $SKILL_DIR — set MB_SKILLS_ROOT" >&2; exit 2; }
0. Validate arguments
Parse $ARGUMENTS into <type> <topic>. Allowed type: feature, fix, refactor, experiment. If type is missing or not in the allowed set, stop and ask the user. If topic is empty, stop and ask.
Hierarchy reminder: Phase → Sprint → Stage. See
references/templates.md§ Plan decomposition for sizing rules. Cyrillic «Этап / Спринт / Фаза» — legacy alias; the scaffold script will soft-warn if you use them in<topic>.
1. Preparation
Read before you start:
~/.claude/CLAUDE.md— global rules$SKILL_DIR/references/templates.md— the "Plan decomposition — Phase → Sprint → Stage" section (what a stage is, when to add one)./RULES.MD(project-level, if present) — project-specific decomposition rules./.memory-bank/roadmap.md— current priorities (if present)./.memory-bank/checklist.md— current tasks (if present)./.memory-bank/lessons.md— known anti-patterns (if present)./.memory-bank/codebase/*.md— stack / architecture / conventions / concerns summaries (if populated)
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.
- 2d ago Changed · +7 lines 3f17944877f9
- 13d ago Changed · +1 lines · +24 tokens per session ef79c2aa8be5
- 22d ago Changed · +10 lines cda77480028a
- 1mo ago First seen · 168 lines · 14 tokens per session scan A e7fd86de0b47
plan is a command published in the GitHub repository fockus/skill-memory-bank (28 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 2,578 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.