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/Enovatr-Labs/SpecRouteWrote 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/enovatr-labs/specroute/review-spec)<a href="https://agentmods.dev/commands/enovatr-labs/specroute/review-spec"><img src="https://agentmods.dev/badge/commands/enovatr-labs/specroute/review-spec/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/enovatr-labs/specroute/review-spec"><img src="https://agentmods.dev/badge/commands/enovatr-labs/specroute/review-spec.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.00023 | $0.00275 |
| Opus 5 | $0.00012 | $0.00138 |
| Sonnet 5 | $0.00005 | $0.00055 |
| Haiku 4.5 | $0.00002 | $0.00028 |
Grade A, and why
review-spec 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 11d 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
Run a readiness review of the planning artifact at $ARGUMENTS before any code work starts. This is the deterministic, user-invokable wrapper around the spec-reviewer checklist.
What this command does
- Reads the artifact at the given path (and its nearest template/README for the applicable contract).
- Applies the spec-reviewer checklist below.
- Reports blocking gaps first, then non-blocking cleanups, then a one-line verdict.
Checklist
- Goal, audience, and scope are stated in plain language; non-goals prevent scope creep.
- Success metrics and acceptance criteria are present, measurable, and testable.
- Requirements use stable IDs; every task back-references a requirement or states its rationale.
- Design covers interfaces, data flow, and failure modes.
- No unresolved placeholders or unowned decisions remain (placeholders are acceptable only in templates).
- Validation covers functional, security, performance, and rollout concerns where relevant.
Output
## Findings
- High: <blocking issue with path:line>
- Medium: <important non-blocking issue>
- Low: <cleanup>
## Ready?
<yes/no> for implementation, with one sentence explaining why.
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.
- 11d ago First seen · 33 lines · 23 tokens per session scan A fdd19434a5d5
review-spec is a command published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 275 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-31.
Other commands, from other repositories
sdd-apply
Implement SDD tasks — writes code following specs and design.
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
icpg-bootstrap
Infer ReasonNodes from existing git commit history. One-time setup for existing codebases.
atomic-plan
Write a design doc (concepts, business rules, approaches) and a checkpoint-table spec (contract) for non-trivial work; inline spec only for trivial. Gauges triviality; loops spec authoring with subagents. Human-facing artifact, Mermaid diagrams allowed.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
session-report
Capture what changed this session and why, scoped to the current branch. Read by ship verbs when synthesizing the commit message; deleted after a successful commit.