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/sdd)<a href="https://agentmods.dev/commands/fockus/skill-memory-bank/sdd"><img src="https://agentmods.dev/badge/commands/fockus/skill-memory-bank/sdd/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/sdd"><img src="https://agentmods.dev/badge/commands/fockus/skill-memory-bank/sdd.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.00044 | $0.05173 |
| Opus 5.5 | $0.00018 | $0.02069 |
| Sonnet 5.5 | $0.00009 | $0.01035 |
| Haiku 4.5 | $0.00004 | $0.00517 |
Grade A, and why
sdd 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 today.
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 — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mb sdd
Generate a Kiro/Kilo-compatible spec triple under .memory-bank/specs/<topic>/. Each file has a single concern: requirements (Kiro User Stories + EARS acceptance criteria — hybrid format), design (architecture + interfaces + decisions + Eval declarations), tasks (numbered <!-- mb-task:N --> work items with **Eval:** / **Scope:** / **Budget:**).
/mb sdd is a generation pipeline, not a blank scaffolder: it reads the discuss/self-interview transcript, generates full content, gates the size, publishes the triple as draft, and runs the deterministic C8 self-check battery before anything is called ready. The raw scaffold writer still exists for direct use (see Scaffold boundary).
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; }
Hybrid requirements format
requirements.md pairs the two industry conventions instead of choosing one:
- Kiro User Story per requirement —
### Requirement N+**User Story:** As a <role>, I want <feature>, so that <benefit>.(the "who / why"). - EARS acceptance criteria under each — a
#### Acceptance Criteriaheading with- **REQ-NNN**: WHEN ... THE SYSTEM SHALL ...bullets in the 5 EARS patterns, uppercase keywords (the testable "what").mb-ears-validate.shis case-insensitive and validates only these bullets; User-Story lines are ignored, so the two layers coexist with zero tooling conflict.
REQ-IDs stay unique and traceable; mb-traceability-gen.sh and **Covers:** REQ-NNN in tasks.md are unaffected by the grouping.
Why split into three?
- Parallel work — requirements / design / tasks evolve at different speeds.
requirements.mdstays self-contained and exportable to Kiro.tasks.mdis checkbox-compatible with downstream tools.mb-traceability-gen.shautomatically picks up REQ-IDs fromspecs/*/requirements.mdfor the REQ → Plan → Test matrix.
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.
- today Changed · +4 lines bcac0f8c375d
- 11d ago Changed · +24 tokens per session 62864e16c21c
- 20d ago Changed · +10 lines 769473c0ecfb
- 1mo ago First seen · 223 lines · 20 tokens per session scan A 027cd1f93c23
sdd is a command published in the GitHub repository fockus/skill-memory-bank (26 stars, last pushed yesterday), licensed MIT. It adds 44 tokens to every session and 5,173 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
dashboard
Show the repo dashboard: the pinned index of every open map, the whiteboard, and live counts.
pause
Checkpoint the ticket in play so it can be resumed later.
resume
Resume a paused ticket from its checkpoint.
whiteboard
Show the whiteboard: loose (map-less) tickets, their frontier and who holds each.
work
Work the next frontier ticket, or the one you name.
prune
Prune a map's closed and orphan sub-issue edges to reclaim slots under GitHub's 100-cap (references kept).