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/agents/enovatr-labs/specroute/readme)<a href="https://agentmods.dev/agents/enovatr-labs/specroute/readme"><img src="https://agentmods.dev/badge/agents/enovatr-labs/specroute/readme/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/agents/enovatr-labs/specroute/readme"><img src="https://agentmods.dev/badge/agents/enovatr-labs/specroute/readme.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.00000 | $0.01428 |
| Opus 5.5 | $0.00000 | $0.00571 |
| Sonnet 5.5 | $0.00000 | $0.00286 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade A, and why
README 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 2mo 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SpecRoute Implementation Agents
This directory contains the 12 Claude Code agents that implement the SpecRoute skeleton. They are project-internal - they build SpecRoute itself, not consumer-facing templates that ship as artifacts.
Consumer-facing agent templates live separately in agents/ (the SpecRoute artifact directory), with reference layouts in runtimes/.claude/agents/.
Roster
Verified against disk on 2026-07-27. Model and Color below are copied from each file's frontmatter; Owns summarizes each file's ## Owns section. Department is a README-only grouping - agent files carry no department field.
| Agent | Department | Model | Color | Memory | Owns |
|---|---|---|---|---|---|
prd-author |
Specification | opus | blue | - | prds/ - PRD templates, lifecycle, examples |
spec-author |
Specification | opus | cyan | - | specs/ - spec triplet (requirements/design/tasks), feature/technical specs, ADRs |
agent-roster-architect |
Specification | opus | purple | - | agents/ - agent template, archetypes, examples, cross-vendor roster |
skill-author |
Implementation | opus | green | - | skills/ - folder-per-skill SKILL.md template + examples |
prompt-engineer |
Implementation | opus | yellow | - | prompts/ - global/phase/task master-prompt templates + per-vendor prompts |
command-author |
Implementation | sonnet | orange | - | commands/ - Claude Markdown + Gemini TOML command templates |
hooks-author |
Implementation | sonnet | red | - | hooks/ - Claude hooks.template.json + Kiro examples at hooks/kiro/examples/*.json |
runtime-architect |
Integration | opus | pink | project | runtimes/, tools/sync-skills.py - per-vendor runtime layouts + MCP single-source + cross-vendor sync |
framework-docs-author |
Documentation | opus | blue | project | agentic-docs/, workflows/, root context files (README, CLAUDE.md, GEMINI.md, AGENTS.md) |
sanitization-auditor |
Quality | opus | red | project | Pre-commit / pre-PR audits - blocks any private-project leak |
template-quality-reviewer |
Quality | sonnet | yellow | - | Template quality bar - production-grade, immediately usable, has worked examples |
docs-currency-auditor |
Quality | opus | orange | project | Vendor facts, version anchors, transition dates, counts that must match disk, cross-mirror consistency |
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.
- 2mo ago First seen · 64 lines · 0 tokens per session scan A 8afa1bcdfea4
README is an agent published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed yesterday), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,428 tokens. 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 agents, from other repositories
bootstrap
Use once per invocation, at the start of a new Hedgehog project, to land the workspace for whichever core planner selected at Phase 0 — the first real workspace this project gets, since init with no explicit core flag lands the shared agents/skills/build-graph payload and leaves the workspace to bootstrap. Reads the…
doc-onboard
Discovery and understanding of a codebase. Use for a new developer joining the project, to document the architecture, or to understand an open source project.
Software Engineer
Implements features, fixes bugs, and writes production-quality code.
ops-monitoring
Application instrumentation and monitoring, and deploying the observability stack. Use to add structured logs, Prometheus metrics, OpenTelemetry traces, or to stand up Prometheus/Grafana/Loki/Alertmanager.
ops-deps
Audit and analysis of dependencies. Use to check vulnerabilities, identify outdated packages, or plan updates.
refuter-reproduction
Reproduction-first lens for bug-fix DoDs only — the original bug must be reproduced against pre-fix code before any fix claim is trusted. Read-only. Invoked only by mnm-verify, only when the DoD's Goal is a bug fix.