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/mrvladd-d/memobank/spec-initgit 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-init)<a href="https://agentmods.dev/commands/mrvladd-d/memobank/spec-init"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/spec-init.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 | $0.00015 | $0.01080 |
| Opus 5 | $0.00008 | $0.00540 |
| Sonnet 5 | $0.00003 | $0.00216 |
| Haiku 4.5 | $0.00002 | $0.00108 |
Grade A, and why
spec-init 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec-init - Lightweight SDD route map bootstrap
/spec-init is a pre-PRD bootstrap/preflight, not a design phase. It identifies only evidence-backed or explicitly uncertain design areas, expected spec locations, gaps, and open questions. It does not run an architecture interview, design architecture, define source-of-truth hierarchy, set backbone status, write OpenAPI policy, create diagrams, or create authoritative architecture, contracts, states, data, or domain specs.
Real SDD backbone design belongs to /spec-design after /prd. Feature-level design belongs to /spec-improve FT-<NNN>.
0) Position in workflow
Run after clarified /write-prd and before /prd.
Canonical manual chain:
/analysis -> /brief -> /constitution -> /write-prd -> /spec-init -> /prd -> /spec-design -> /spec-improve FT-001 -> /prd-to-tasks FT-001.
1) Inputs
Read, if present:
.memory-bank/constitution.md.memory-bank/analysis/product-brief.md.memory-bank/prd.md- existing
.memory-bank/spec-index.md - existing specs under
.memory-bank/architecture/,.memory-bank/tech-specs/,.memory-bank/contracts/,.memory-bank/domains/,.memory-bank/states/,.memory-bank/adrs/,.memory-bank/testing/, and.memory-bank/runbooks/
Stop if .memory-bank/prd.md is missing or so unclear that even a lightweight route map would mislead /prd.
2) No architecture interview
Do not conduct an architecture interview in /spec-init.
Rules:
- do not ask architecture, API, data model, state machine, source-of-truth, diagram, or backbone design questions here
- if PRD/brief/existing specs provide evidence, route the area as
authoritative,planned,candidate, ornot_applicable - if evidence is insufficient, mark the area
unknownand add a gap/open question - stop only when the PRD is missing/unclear enough that recording
unknownwould create a misleading route map
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 · 105 lines · 15 tokens per session scan A 3839ce6146a0
spec-init is a command published in the GitHub repository mrvladd-d/memobank (55 stars, last pushed 3mo ago), licensed MIT. It adds 15 tokens to every session and 1,080 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.