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.
npx agentmods add commands/fockus/skill-memory-bank/traceability-gengit 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/traceability-gen)<a href="https://agentmods.dev/commands/fockus/skill-memory-bank/traceability-gen"><img src="https://agentmods.dev/badge/commands/fockus/skill-memory-bank/traceability-gen.svg" alt="Measured on agentmods" 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.00011 | $0.00343 |
| Opus 5 | $0.00005 | $0.00171 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
traceability-gen 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 3d 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.
What it actually says
/mb traceability-gen
Regenerate .memory-bank/traceability.md — the REQ → Plan → Test coverage matrix.
What it does
Scans:
.memory-bank/specs/*/requirements.mdforREQ-NNNdefinitions.memory-bank/plans/*.md+plans/done/*.mdfor:covers_requirements: [REQ-NNN, ...]frontmatter field<!-- covers: REQ-NNN -->inline markers
tests/(repo root) and.memory-bank/tests/forREQ_NNN/REQ-NNNsubstrings
Produces a full-overwrite traceability.md with:
- Coverage summary (Total / Planned / Tested)
- Matrix table
- Orphans section (REQs in spec but no covering plan)
Zero-spec fallback
If no specs/*/requirements.md exists, produces a minimal traceability.md saying
"No specs yet — run /mb sdd <topic> to create requirements." and exits 0.
Usage
Run after adding requirements, wiring covers_requirements: in a plan, or adding REQ-NNN markers to tests. Also runs automatically at the end of /mb plan and /mb done.
bash ~/.claude/skills/memory-bank/scripts/mb-traceability-gen.sh
Exit codes
0— success1—.memory-bank/not found
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.
- 3d ago First seen · 41 lines · 11 tokens per session scan A 2c64a6033d5a
traceability-gen is a command published in the GitHub repository fockus/skill-memory-bank (24 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 343 once invoked, about $0.0001 per session on Opus 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-09-03.
Other commands, from other repositories
checkpoint
Save verification state and progress checkpoint.
epic-validate
Validate epic readiness, dependencies, and coordination policy.
implement
Execute tasks from a track's implementation plan following TDD workflow.
execute
Execute the next available tracked task with TDD, pre-commit validation, PR creation, AI code review, and issue tracker bridge sync.
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.