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/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/forge)<a href="https://agentmods.dev/commands/fabriqaai/specs.md/forge"><img src="https://agentmods.dev/badge/commands/fabriqaai/specs.md/forge/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/fabriqaai/specs.md/forge"><img src="https://agentmods.dev/badge/commands/fabriqaai/specs.md/forge.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.00009 | $0.00276 |
| Opus 5.5 | $0.00004 | $0.00110 |
| Sonnet 5.5 | $0.00002 | $0.00055 |
| Haiku 4.5 | $0.00001 | $0.00028 |
Grade A, and why
forge 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.
What it actually says
Activate Forge
Command: /specsmd-forge
Activation
You are now the Ideation Orchestrator in Forge mode for specsmd.
IMMEDIATELY read and adopt the persona from:
→ .specsmd/ideation/agents/orchestrator/agent.md
Then execute the Forge skill:
→ .specsmd/ideation/agents/orchestrator/skills/forge/SKILL.md
Critical First Steps
- Read Config:
.specsmd/ideation/memory-bank.yaml - Read Interaction Protocol:
.specsmd/ideation/shared/protocols/interaction-adaptation.md - If Flame Report exists: Load shortlisted ideas and begin shaping
- If ideas provided directly: Accept them and begin shaping
- If nothing: Ask "Which ideas would you like to develop into concepts?"
Routing Targets
- Back to Orchestrator:
/specsmd-ideation - To Spark:
/specsmd-spark - To Flame:
/specsmd-flame
Begin
Activate now. Read the Forge skill and start shaping concepts.
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 · 44 lines · 9 tokens per session scan A 687066d4170f
forge is a command published in the GitHub repository fabriqaai/specs.md (219 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 276 once invoked, about $0.0000 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
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.bug.assess
Assess a bug report (pasted text or URL) against the codebase and produce an assessment with possible remediation.
speckit.assess.intake
Capture and normalize a raw idea (text, URL, ticket, or codebase pointer) into an intake note.
speckit.github.taskstoissues
Convert existing tasks into actionable, dependency-ordered GitHub issues for the feature based on available design artifacts.
diff-script
Compare an MDL script against the project's current state.