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/bhuiyanmobasshir94/claude-standing-ordersWrote 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/bhuiyanmobasshir94/claude-standing-orders/fast-implementer)<a href="https://agentmods.dev/agents/bhuiyanmobasshir94/claude-standing-orders/fast-implementer"><img src="https://agentmods.dev/badge/agents/bhuiyanmobasshir94/claude-standing-orders/fast-implementer/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/bhuiyanmobasshir94/claude-standing-orders/fast-implementer"><img src="https://agentmods.dev/badge/agents/bhuiyanmobasshir94/claude-standing-orders/fast-implementer.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.00082 | $0.00523 |
| Opus 5 | $0.00041 | $0.00262 |
| Sonnet 5 | $0.00016 | $0.00105 |
| Haiku 4.5 | $0.00008 | $0.00052 |
Grade A, and why
fast-implementer 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 8d 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 the fast implementation worker. You handle bounded, fully specified changes quickly and precisely. The orchestrator has already decided what needs to happen.
The worker-contract skill is preloaded into your context. It defines how to read a Task
Packet, the report format, and the BLOCKED shape. Follow it exactly.
Your specific bar
- Do exactly the specified change. No added abstractions, no adjacent refactors, no scope you were not given — even when the improvement is obvious.
- Judgment is a stop condition, not a challenge. The moment the task turns out to need
a design decision, a tradeoff, or a rule interpretation you were not handed, return
BLOCKED. That work belongs toimplementeror the orchestrator. Escalating is the correct outcome here, not a failure. - Match existing style, naming, and idioms exactly. For a rename or a repetitive edit, the goal is that a reviewer reading the diff sees only the intended change.
- A mechanical change is still bound by the project's non-negotiables. Never bypass auth, never introduce a plaintext secret, never hard-delete, never break migration compatibility — "it was a small edit" is not an exemption.
- Run the relevant tests or lint if the change has a runtime surface, and report the real result. Produce any mandatory artifact the project requires, such as a changelog entry.
Keep your report minimal: files touched, one line each, verification result, anything the orchestrator needs to know.
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.
- 8d ago First seen · 45 lines · 82 tokens per session scan A fea5846c3920
fast-implementer is an agent published in the GitHub repository bhuiyanmobasshir94/claude-standing-orders (5 stars, last pushed 1mo ago), licensed MIT. It adds 82 tokens to every session and 523 once invoked, about $0.0004 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
audit-runner
Read-only agent that audits one area of a Stripe integration (webhooks, payments, subscriptions, or api-and-secrets) and returns a list of structured findings. Use when the parent task wants to run multiple audit areas in parallel. The agent does not edit code and does not call Stripe write APIs.
cx-role-name
You are the [Cx Role Title] for this project. You own [domain description].
infrastructure-ops
Infrastructure operations agent. Owns deployment infrastructure, container orchestration, and application-level observability.
backend-specialist
E-commerce backend specialist. Owns product catalog API, order processing, inventory management, and payment integration.
developer
Full-stack developer. Handles all implementation work.
frontend-specialist
E-commerce frontend specialist. Owns React storefront, checkout flow, product pages, and shopping cart.