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/mrvladd-d/memobankWrote 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/mrvladd-d/memobank/spec-design)<a href="https://agentmods.dev/commands/mrvladd-d/memobank/spec-design"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/spec-design/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/mrvladd-d/memobank/spec-design"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/spec-design.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.00016 | $0.02377 |
| Opus 5.5 | $0.00006 | $0.00951 |
| Sonnet 5.5 | $0.00003 | $0.00475 |
| Haiku 4.5 | $0.00002 | $0.00238 |
Grade A, and why
spec-design 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 1mo 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec-design - Global SDD backbone gate
The gate is mandatory by workflow, but adaptive by depth:
- simple T0/T1 projects create a minimal backbone and mark irrelevant areas
not_applicable; - projects with shared/T2/T3 concerns get staged architecture decisions and normal backbone specs;
- unresolved key decisions are recorded as blockers and downstream commands must stop.
/spec-design does not create TASK records, implementation plans, or feature-local tech specs, and it does not replace /spec-improve.
0) Input and timing
Run after /prd.
Supported arguments:
- no argument: inspect all current features and update the global backbone
--all: same as no argument; explicit for autonomous or batch flow
Required inputs:
.memory-bank/spec-index.md.memory-bank/requirements.md.memory-bank/epics/.memory-bank/features/- existing relevant specs under
.memory-bank/architecture/,.memory-bank/guides/,.memory-bank/domains/,.memory-bank/contracts/,.memory-bank/states/,.memory-bank/adrs/,.memory-bank/testing/, and.memory-bank/runbooks/
Never skip the command. For small independent T0/T1-only scope, write the minimal backbone status and mark non-applicable areas instead of expanding architecture.
1) Backbone status gate
Update .memory-bank/spec-index.md with a clear global backbone status:
complete: shared/global decisions are recorded and no blocker remainsminimal: project is simple/T0-T1 oriented; unnecessary areas are explicitlynot_applicableblocked: key architecture decisions are unresolved
If status is blocked, stop downstream work. Record:
- unresolved decision
- affected features/requirements
- why a conservative assumption would be unsafe
- next question or owner needed
2) Spec-index content contract
.memory-bank/spec-index.md is an index and route map, not an authoritative design spec.
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.
- 1mo ago First seen · 187 lines · 16 tokens per session scan A 7f599935e30a
spec-design is a command published in the GitHub repository mrvladd-d/memobank (56 stars, last pushed 4mo ago), licensed MIT. It adds 16 tokens to every session and 2,377 once invoked, about $0.0001 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.