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/marcusgoll/Spec-FlowWrote 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/marcusgoll/spec-flow/routing)<a href="https://agentmods.dev/agents/marcusgoll/spec-flow/routing"><img src="https://agentmods.dev/badge/agents/marcusgoll/spec-flow/routing/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/marcusgoll/spec-flow/routing"><img src="https://agentmods.dev/badge/agents/marcusgoll/spec-flow/routing.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.01797 |
| Opus 5.5 | $0.00000 | $0.00719 |
| Sonnet 5.5 | $0.00000 | $0.00359 |
| Haiku 4.5 | $0.00000 | $0.00180 |
Grade A, and why
ROUTING 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.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Routing Guide
When to use which agent for implementation work
Quick Decision Tree
Is this a workflow phase (spec, plan, tasks, optimize, ship)?
├── Yes → Use PHASE AGENT (spec-agent, plan-agent, etc.)
└── No → Continue...
Is domain-memory.yaml present?
├── Yes → Use WORKER (domain/worker.md)
│ Worker reads domain memory, picks ONE feature, implements, exits
└── No → Continue...
Is this sprint-level work in an epic?
├── Yes → Use SPECIALIST based on sprint domain:
│ • Backend-only sprint → backend-dev
│ • Frontend-only sprint → frontend-dev
│ • Database sprint → database-architect
│ • Testing sprint → qa-test
│ • Mixed/unclear → general-purpose
└── No → Use WORKER with initialized domain memory
Agent Categories
1. Phase Agents (Workflow Orchestration)
Location: .claude/agents/phase/*-agent.md
When to use: Always spawned by orchestrator commands (/feature, /epic), never directly.
| Agent | Spawned By | Purpose |
|---|---|---|
| spec-agent | /feature, /epic | Generate specification |
| clarify-agent | /clarify | Resolve ambiguities |
| plan-agent | /plan | Create implementation plan |
| tasks-agent | /tasks | Break down into TDD tasks |
| optimize-agent | /optimize | Run quality gates |
| ship-agent | /ship | Handle deployment |
| finalize-agent | /finalize | Archive and document |
Key trait: Return structured results (---COMPLETED---, ---NEEDS_INPUT---, ---FAILED---)
2. Worker Agent (Atomic Implementation)
Location: .claude/agents/domain/worker.md
When to use:
domain-memory.yamlexists in feature/sprint directory- Implementing individual features from a backlog
- Default for
/implementphase
How it works:
- Reads domain-memory.yaml
- Picks ONE failing/untested feature
- Implements with TDD
- Updates domain-memory.yaml
- Commits and EXITs (even if more work remains)
Key trait: Atomic, stateless, disciplined. Never works on more than one feature.
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 · 228 lines · 0 tokens per session scan A 5dfb50344e9c
ROUTING is an agent published in the GitHub repository marcusgoll/Spec-Flow (96 stars, last pushed 22d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,797 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-30.
Other agents, from other repositories
bash-expert
Master of defensive Bash scripting for production automation, CI/CD pipelines, and system utilities. Expert in safe, portable, and testable shell scripts.
technical-director
High-level technical decisions — engine architecture, technology choices, performance strategy, technical risk, cross-system conflicts.
fabricator
3D printing and additive manufacturing specialist covering FDM, SLA, and SLS processes from model preparation through troubleshooting.
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
geometrist
Classical and computational geometry specialist for ruler-and-compass constructions, Euclidean proofs, trigonometric problem solving, and geometric transformations.