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/configgit clone --depth 1 https://github.com/fockus/skill-memory-bankWhat 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 | $0.00012 | $0.01207 |
| Opus 5 | $0.00006 | $0.00603 |
| Sonnet 5 | $0.00002 | $0.00241 |
| Haiku 4.5 | $0.00001 | $0.00121 |
Grade A, and why
config 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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mb config
Manage the project's execution pipeline.yaml — the declarative config consumed by /mb work. Defines roles → agents mapping, local workflow modes (workflow.default + workflows.*), per-item loops, severity gates, sprint context guard, review rubric, and SDD enforcement policy.
Why pipeline.yaml?
/mb work <target> resolves a named workflow from pipeline.yaml, defaulting to execution (implement → verify → done — review is off by default). Opt into review/judge per run (--review/--judge) or persist with review.enabled: true / <stage>.enabled: true; projects can also select full (the whole chain), governed-execution, full-cycle, planning-only, review-only, or custom loops with different max_cycles. Different teams need different defaults — review severity tolerance, max review cycles, role-to-agent mapping, protected-paths policy. Hard-coding these would lock the engine. pipeline.yaml makes them per-project and version-controlled.
Resolution
Effective config = first match wins:
<bank>/pipeline.yaml(project override, if present)references/pipeline.default.yaml(shipped default)
The shipped default is always present and self-validates. Projects do not need to run init until they want to override something.
Subcommands
| Subcommand | Description |
|---|---|
init [--force] |
Copy bundled default into <bank>/pipeline.yaml. Refuses if file exists unless --force is given. |
show |
Print effective config (project override → default fallback). |
path |
Print absolute path to the effective config file. |
validate [yaml_file] |
Structural schema check (spec §9). Without an argument: validate the resolved file. With a file argument: validate that file directly. |
All subcommands accept an optional trailing [mb_path] to point at an alternative bank location.
Behavior
initwrites a byte-for-byte copy ofreferences/pipeline.default.yamlinto<bank>/pipeline.yaml. Idempotency guard refuses overwrite without--force.showcats the resolved file as-is (preserves comments).pathprintsrealpathof the resolved file.validaterunsscripts/mb-pipeline-validate.shagainst the resolved (or explicit) path. Exit 0 means schema-clean; exit 1 dumps[validate] <key>: <reason>lines to stderr.
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 · 97 lines · 12 tokens per session scan A add57f45eaa7
config is a command published in the GitHub repository fockus/skill-memory-bank (25 stars, last pushed 1mo ago), licensed MIT. It adds 12 tokens to every session and 1,207 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-08-30.
Other commands, from other repositories
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.
release
The pre-tag controller: version sync, changelog, clean tree, gate, and suite — every failure listed, the tag printed, never run.
security
The security pass: secrets (blocking), SAST, dependency vulns — plus the index's entry points to review from.
init
Install the formatters this repository needs, with every command visible before it runs.
vitaecontext-github
Audit or improve GitHub profile and repository SEO.
test
Run the test suite for the given package and summarize failures.