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/status)<a href="https://agentmods.dev/commands/enovatr-labs/specroute/status"><img src="https://agentmods.dev/badge/commands/enovatr-labs/specroute/status/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/status"><img src="https://agentmods.dev/badge/commands/enovatr-labs/specroute/status.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.00025 | $0.00566 |
| Opus 5 | $0.00013 | $0.00283 |
| Sonnet 5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
status 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 9d 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
Report the SpecRoute skeleton state at a glance. Run these checks and summarize the output as a status table.
echo "── top-level directory status ──"
# Keep this list in sync with EXPECTED_DIRS in .claude/hooks/session-start-status.sh.
# Ground truth: ls -d */
for d in agentic-docs prds specs agents skills commands hooks prompts workflows rules runtimes examples tools assets scripts wiki; do
if [ -d "$d" ]; then
n=$(find "$d" -type f \( -name "*.md" -o -name "*.json" -o -name "*.toml" -o -name "*.yaml" -o -name "*.yml" -o -name "*.sh" -o -name "*.py" \) 2>/dev/null | wc -l | tr -d ' ')
echo " ✓ $d/ ($n files)"
else
echo " ✗ $d/ (missing)"
fi
done
echo
echo "── runtime layouts ──"
for v in claude codex gemini kiro cursor devin; do
if [ -d "runtimes/.$v" ]; then
echo " ✓ runtimes/.$v/"
else
echo " ✗ runtimes/.$v/ (not yet wired)"
fi
done
echo
echo "── implementation agents ──"
if [ -d ".claude/agents" ]; then
find .claude/agents -maxdepth 1 -name "*.md" -not -name "README.md" -exec basename {} .md \; | sort
fi
echo
echo "── outstanding TODOs in tracked files ──"
git grep -n "TODO" 2>/dev/null | wc -l | xargs echo "TODO count:"
echo "(top 10):"
git grep -n "TODO" 2>/dev/null | head -10
echo
echo "── git state ──"
git status --short
git log --oneline -5
Summarize as:
- Overall completion:
<built>/<expected>top-level dirs,<built>/6runtime layouts. - The implementation agents (compare against
.claude/agents/README.md; note any missing). - TODO count and the top items.
- Git: branch, uncommitted changes, recent commits.
Keep the report under ~30 lines of output. The point is orientation, not exhaustive listing.
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.
- 9d ago First seen · 56 lines · 25 tokens per session scan A 04bffd961c3b
status is a command published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 25 tokens to every session and 566 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-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
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.
review
Review the current diff against project memory.
statusline
Show the governor fleet in your Claude Code statusline. Explicit, opt-in, and chains — it never replaces an existing statusline.