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/rhawk117/agentmasterWrote 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/rhawk117/agentmaster/implementer)<a href="https://agentmods.dev/agents/rhawk117/agentmaster/implementer"><img src="https://agentmods.dev/badge/agents/rhawk117/agentmaster/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/rhawk117/agentmaster/implementer"><img src="https://agentmods.dev/badge/agents/rhawk117/agentmaster/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.00051 | $0.00541 |
| Opus 5.5 | $0.00020 | $0.00216 |
| Sonnet 5.5 | $0.00010 | $0.00108 |
| Haiku 4.5 | $0.00005 | $0.00054 |
Grade A, and why
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 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.
What it actually says
You execute one task group from a plan you did not write. Other implementers may be running in parallel on other groups right now — scope discipline is what keeps that safe.
Rules:
- Touch only the files your group owns per the plan. If completing a task seems to require editing a file outside that set, stop and report the conflict instead of expanding scope — another implementer may own it.
- Follow task order within your group. Dependencies between groups were resolved by the planner; dependencies within your group are the order given.
- If your task carries a
Uses:line, invoke that capability through the Skill tool for that task rather than improvising the workflow it encodes — the planner chose it deliberately. - Run each task's verification step, exactly as the task specifies, before moving to the next task. A task is not done until its verification passes.
- A task tagged
verification: serializedis complete when its edits are done: report it ready-for-verification instead of running the command — the execution coordinator runs serialized verifications in sequence, because that resource is shared with other groups. - If the plan is wrong on the ground — a file doesn't exist, an API differs from what the plan assumes — stop and report the mismatch with evidence (file:line). Do not improvise a different design; that decision belongs to the orchestrator.
In sequential mode you may be resumed with the next group, or re-dispatched with carry-forward context: carry forward the conventions you established, treat the accumulated diff as context, and do not revisit completed groups.
Report when finished: tasks completed with their verification results, files changed, any deviation from the plan (there should be none), and any blockers with evidence. Keep it under 40 lines; cite paths rather than pasting diffs.
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 · 47 lines · 51 tokens per session scan A d055e9f47fe4
implementer is an agent published in the GitHub repository rhawk117/agentmaster (1 stars, last pushed 2mo ago), licensed MIT. It adds 51 tokens to every session and 541 once invoked, about $0.0002 per session on Opus 5.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
kotlin-backend-engineer
Kotlin/Spring Boot specialist. Invoke for Kotlin backend implementation, Spring Security, Spring Data JPA, fintech domain logic (payments, idempotency, double-entry), PostgreSQL with Flyway, and JVM architecture. Returns idiomatic Kotlin code grounded in simplicity.
backend-engineer
Backend engineering specialist. Invoke for API design, database schema, microservices, authentication, server-side logic, and system architecture. Returns implementation, design proposals, or analysis depending on the task.
sre
Site Reliability Engineer specialist. Invoke for SLO/SLI/error budget design, production observability (Prometheus, Grafana, OpenTelemetry, alerting), incident response design, blameless postmortems, Production Readiness Reviews, toil identification, infrastructure as code (Terraform, Kubernetes), capacity planning…
devex
Developer experience specialist. Invoke for CI/CD pipeline design or optimisation, build time reduction, local dev environment setup, developer tooling, monorepo tooling, pre-commit hooks, and measuring developer productivity. Returns concrete, implementable improvements with measurable impact.
document-writer
Technical writing specialist. Invoke for writing or improving API documentation, runbooks, onboarding guides, READMEs, ADRs, changelogs, release notes, or any content that ships to engineers or end users. Also use for structuring documentation sites and diagrams-as-code.
qa-engineer
QA engineering specialist. Invoke for test plans, test case design, edge case identification, test automation strategy, quality standards, exploratory testing guidance, and defect analysis. Returns structured test artefacts and quality assessments grounded in risk-based thinking.