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 skills/fabriqaai/specs.md/routenpx skills add fabriqaai/specs.md --skill routegit 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/skills/fabriqaai/specs.md/route)<a href="https://agentmods.dev/skills/fabriqaai/specs.md/route"><img src="https://agentmods.dev/badge/skills/fabriqaai/specs.md/route.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.1 | $0.00017 | $0.01032 |
| Opus 5 | $0.00009 | $0.00516 |
| Sonnet 5 | $0.00003 | $0.00206 |
| Haiku 4.5 | $0.00002 | $0.00103 |
Grade A, and why
route 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 6d 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
<file_system_scan critical="true">
Use these EXACT glob patterns:
<pattern purpose="Find intent briefs">
.specs-fire/intents/*/brief.md
</pattern>
<pattern purpose="Find work items">
.specs-fire/intents/*/work-items/*.md
</pattern>
Work items are {work-item-id}.md files directly in work-items/ folder.
</file_system_scan>
<action>Reconcile: add discovered items to state as pending</action>
<action>Parse current project state</action>
Plan run scope and start execution? [Y/n]
</output>
<check if="response == y">
<route_to>builder-agent (run-plan)</route_to>
</check>
<stop/>
</check>
Work items delivered:
{list completed work items}
Ready for next intent? [Y/n]
</output>
</check>
What do you want to build?
</output>
<route_to>planner-agent (intent-capture)</route_to>
<routing_decision_tree>
state.yaml + file system scan
│
├── runs.active? ─────────────> Builder (run-execute, resume)
│
├── pending work items? ──────> Builder (run-plan, then execute)
│
├── intent without work items? > Planner (work-item-decompose)
│
└── no active intents ────────> Planner (intent-capture)
</routing_decision_tree>
<context_passed_to_agents> To Planner:
context:
action: intent-capture | work-item-decompose
intent_id: {if decomposing}
To Builder:
context:
action: run-plan | run-execute | resume
pending_items: [{list of pending work items}] # for run-plan
run_id: {if resuming}
</context_passed_to_agents>
<success_criteria> File system scanned for untracked intents/work-items State reconciled with file system Correct agent selected based on state Context passed to target agent </success_criteria>
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.
- 6d ago First seen · 147 lines · 17 tokens per session scan A f5cb32a78799
route is a skill published in the GitHub repository fabriqaai/specs.md (206 stars, last pushed 13d ago), licensed MIT. It adds 17 tokens to every session and 1,032 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 skills, from other repositories
acceptance-orchestrator-v2
Acceptance Orchestrator workflow skill. Use this skill when the user needs a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention and the operator should preserve the upstream workflow, copied support files…
acceptance-orchestrator
Acceptance Orchestrator workflow skill. Use this skill when the user needs a coding task should be driven end-to-end from issue intake through implementation, review, deployment, and acceptance verification with minimal human re-intervention and the operator should preserve the upstream workflow, copied support files…
swarm-advanced
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows.
agent-harness-fault-injection
Use when an agent workflow needs deterministic recovery evidence for sandbox, MCP/tool, worker, checkpoint, memory, or orchestration failures.
agenttrace-session-audit
Audit local AI coding-agent sessions with agenttrace for cost, tool failures, latency, anomalies, health, diffs, and CI gates.
akf-trust-metadata
The AI native file format. EXIF for AI — stamps every file with trust scores, source provenance, and compliance metadata. Embeds into 20+ formats (DOCX, PDF, images, code). EU AI Act, SOX, HIPAA auditing.