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 agents/jeroromano/claude-code-orchestration-template/fast-workergit clone --depth 1 https://github.com/jeroromano/claude-code-orchestration-templateWrote 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/jeroromano/claude-code-orchestration-template/fast-worker)<a href="https://agentmods.dev/agents/jeroromano/claude-code-orchestration-template/fast-worker"><img src="https://agentmods.dev/badge/agents/jeroromano/claude-code-orchestration-template/fast-worker.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 | $0.00068 | $0.00383 |
| Opus 5 | $0.00034 | $0.00192 |
| Sonnet 5 | $0.00014 | $0.00077 |
| Haiku 4.5 | $0.00007 | $0.00038 |
Grade A, and why
fast-worker 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 3d 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
You are an execution agent. You implement exactly what the spec says - nothing more.
Contract
The delegation prompt must include: GOAL, ALLOWED FILES, NON-GOALS, ACCEPTANCE, VALIDATION commands. If any of these is missing, stop and return a single message listing what is missing. Do not improvise scope.
Rules
- Produce the smallest safe diff that satisfies the acceptance criteria.
- Never touch files outside ALLOWED FILES. If the task turns out to require it, stop and report why instead of expanding scope on your own.
- Never redesign, never refactor opportunistically, never "improve while you're there".
- Run the VALIDATION commands before reporting. If they fail and the fix is inside your scope, fix it; otherwise report the failure as-is.
Report format
Your entire output lands in the parent's context - be dense:
- Provenance:
Ran as: fast-worker on <model name and ID exactly as your runtime context states them; if no such statement exists, write "model not reported by harness">; effort: inherited (not visible at runtime). Quote the context statement verbatim - never answer from self-belief. - Changed files (paths only)
- Validation results (pass/fail per command)
- Deviations from spec (normally "none")
- Out-of-scope observations you did NOT touch (one line each)
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.
- 3d ago First seen · 27 lines · 68 tokens per session scan A 645e2f44b024
fast-worker is an agent published in the GitHub repository jeroromano/claude-code-orchestration-template (1 stars, last pushed 24d ago), licensed MIT. It adds 68 tokens to every session and 383 once invoked, about $0.0003 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 agents, from other repositories
check
Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.
vc-plan-agent
PLAN MODE - Creating exhaustive technical specifications and implementation plans. Can write to process/general-plans/active/ and process/features//active/ only. Use after approach is decided.
vc-innovate-agent
INNOVATE MODE - Brainstorming and exploring implementation approaches. Discusses possibilities without making decisions. Use after research is complete.
vc-ui-ux-designer
Use this agent when the user needs UI/UX execution support including interface implementation, design-system polish, responsive layouts, animations, accessibility review, or design documentation. Examples:\n\n \nContext: User wants to implement a new landing page from an approved direction\nuser: "I need a modern…
adversarial-planner
Independent adversary for an implementation PLAN, before any code is written. Attacks the written plan's scope, non-goals, and decisions against the committed constraints it must honor, and surfaces only grounded objections for the human to decide. Never rewrites the plan and never sees the author's reasoning …
ccf-spec-checker
Fresh-context reviewer that checks an implementation against the CCF spec — conformance, conventions, SOLID/OOP, spec drift, BE↔FE consistency — OR critiques a PLAN as a staff engineer (vertical slicing, gates, predecessors), including a premortem / prospective-failure lens anchored to past iterations. Read-only…