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-autogit 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-auto)<a href="https://agentmods.dev/commands/mrvladd-d/memobank/spec-auto"><img src="https://agentmods.dev/badge/commands/mrvladd-d/memobank/spec-auto.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.01218 |
| Opus 5 | $0.00008 | $0.00609 |
| Sonnet 5 | $0.00003 | $0.00244 |
| Haiku 4.5 | $0.00002 | $0.00122 |
Grade A, and why
spec-auto 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 5d 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/spec-auto - Autonomous SDD design
Supported arguments:
--initFT-<NNN>--all
0) Mode
/spec-auto never asks the user questions.
It asks and answers internal design questions itself, records assumptions, and makes conservative/KISS decisions from:
.memory-bank/constitution.md.memory-bank/analysis/product-brief.md.memory-bank/prd.md.memory-bank/spec-index.md.memory-bank/requirements.md.memory-bank/epics/.memory-bank/features/- existing specs
If a contradiction or ambiguity is unsafe/blocking, record a blocker and stop with the terminal state expected by the active autonomous workflow.
1) Arguments
--init: run autonomous spec-index initialization after/write-prdand before/prdFT-<NNN>: run autonomous feature-level design for one feature after/prd--all: require or run autonomous backbone after/prd, then run autonomous feature-level design for every targeted feature
If no argument is provided, infer:
- before
/prd, use--init - after
/prd, use--all; run or require/spec-design --allfirst - if unclear, stop and report the missing argument
2) --init
Perform lightweight /spec-init behavior:
- read Constitution, Product Brief, PRD, existing spec-index, and existing specs
- update
.memory-bank/spec-index.mdas the pre-PRD SDD route map - mark areas as planned/candidate/unknown/not_applicable only from PRD/brief/existing-spec evidence
- record assumptions and open questions
- do not run architecture design, set backbone status, create diagrams, define source-of-truth hierarchy, or create authoritative design specs unless existing evidence already contains the decision
If the skeleton would be misleading without unavailable user input:
- record
BLOCKER: misleading spec-index risk - in autonomous flow set terminal state
HALT_BLOCKING_QUESTIONS - stop before
/prd
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.
- 5d ago First seen · 107 lines · 15 tokens per session scan A 24afc77b697b
spec-auto 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,218 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.