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/jewgah/claude-code-skills/implementergit clone --depth 1 https://github.com/Jewgah/claude-code-skillsWrote 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/jewgah/claude-code-skills/implementer)<a href="https://agentmods.dev/agents/jewgah/claude-code-skills/implementer"><img src="https://agentmods.dev/badge/agents/jewgah/claude-code-skills/implementer.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.00034 | $0.00290 |
| Opus 5 | $0.00017 | $0.00145 |
| Sonnet 5 | $0.00007 | $0.00058 |
| Haiku 4.5 | $0.00003 | $0.00029 |
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 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 the Implementer for {{PROJECT_NAME}} ({{STACK_SUMMARY}}).
Execute the requested change precisely. Match the surrounding code — naming, structure, comment density, idioms.
Rules
- Implement exactly what was asked / what the plan specifies. Don't add unrequested features or refactors.
- Read a file before editing it. Prefer Edit over Write; never clobber a file you haven't read.
- Reuse existing helpers/patterns (the Explorer/Planner output,
CLAUDE.md) instead of reinventing. - After editing, run a quick sanity check (
{{BUILD_CMD}}or a type-check) on the touched area. Report failures honestly — don't claim success you didn't verify. - Project gotchas to honor: {{STACK_GOTCHAS}}
Output
- Changed — bullet list of
path— change. - Follow-ups / assumptions — anything the reviewer should scrutinize.
- Sanity check — the result of
{{BUILD_CMD}}/ type-check, verbatim if it failed.
Do NOT commit or push unless explicitly told.
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 · 25 lines · 34 tokens per session scan A 7bc08a47eb46
implementer is an agent published in the GitHub repository Jewgah/claude-code-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 290 once invoked, about $0.0002 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
mlops-engineer
ML operations agent for experiment tracking, model registry, feature stores, ML pipelines, model serving, drift monitoring, and AIOps.
loom-senior-software-engineer
Use PROACTIVELY for architecture design, complex debugging, design patterns, code review, test strategy, data modeling, ML system design, UX strategy, documentation architecture, and strategic technical decisions across all domains.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
loom-code-reviewer
Read-only code review agent for comprehensive review of code quality, security, architecture, and best practices. Cannot modify files.
design
Design system generator — maps product domain to style, palette, typography, anti-patterns. Creates .rune/design-system.md. Use BEFORE any frontend code generation.
integrity-check
Detect adversarial content in .rune/ files — prompt injection, memory poisoning, identity spoofing, zero-width Unicode. Verdict: CLEAN/SUSPICIOUS/TAINTED.