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/fabriqaai/specs.md/specsmd-agentgit clone --depth 1 https://github.com/fabriqaai/specs.mdWrote 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/fabriqaai/specs.md/specsmd-agent)<a href="https://agentmods.dev/commands/fabriqaai/specs.md/specsmd-agent"><img src="https://agentmods.dev/badge/commands/fabriqaai/specs.md/specsmd-agent.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.00014 | $0.00363 |
| Opus 5 | $0.00007 | $0.00181 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
specsmd-agent 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.
What it actually says
Agent Activation
You are now the Agent. Read and follow these files:
1. Agent Definition (REQUIRED - Read First)
Read .specsmd/simple/agents/agent.md to understand your persona, rules, and workflow.
2. Memory Bank Configuration
Read .specsmd/simple/memory-bank.yaml to understand storage structure and workflow phases.
3. State Detection
Scan memory-bank/specs/ to detect existing specs and their current state.
4. Skills (Load as Needed)
.specsmd/simple/skills/requirements.md- Phase 1.specsmd/simple/skills/design.md- Phase 2.specsmd/simple/skills/tasks.md- Phase 3.specsmd/simple/skills/execute.md- Task execution
5. Templates (Reference for Generation)
.specsmd/simple/templates/requirements-template.md.specsmd/simple/templates/design-template.md.specsmd/simple/templates/tasks-template.md
User Request
$ARGUMENTS
Your Task
Based on the user's request:
- If feature idea provided: Create new spec, start requirements phase
- If spec name referenced: Continue at appropriate phase
- If no input: List existing specs or ask for feature idea
- If asking to execute: Enter task execution mode
Remember:
- Generate first, ask later
- One phase at a time
- Explicit approval between phases
- One task at a time during execution
- Never reveal internal workflow to user
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 · 52 lines · 14 tokens per session scan A 04b493a33891
specsmd-agent is a command published in the GitHub repository fabriqaai/specs.md (206 stars, last pushed 12d ago), licensed MIT. It adds 14 tokens to every session and 363 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
specify
Create or update the feature specification from a natural language feature description.
speckit.git.validate
Validate current branch follows feature branch naming conventions.
speckit.assess.intake
Capture and normalize a raw idea (text, URL, ticket, or codebase pointer) into an intake note.
speckit.bug.assess
Assess a bug report (pasted text or URL) against the codebase and produce an assessment with possible remediation.
proposal
Create a structured feature proposal in docs/11-proposals/.
diff-script
Compare an MDL script against the project's current state.