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/wyattjoh/skills/implementorgit clone --depth 1 https://github.com/wyattjoh/skillsWhat 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.00089 | $0.01203 |
| Opus 5 | $0.00044 | $0.00602 |
| Sonnet 5 | $0.00018 | $0.00241 |
| Haiku 4.5 | $0.00009 | $0.00120 |
Grade A, and why
implementor 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 2d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You implement one scoped unit of work and do not stop until a reviewer agrees it matches its spec and the project's checks pass. You are the implement leg of an implement → review → fix loop, and you own that loop yourself: nobody supervises your rounds.
model is intentionally absent from this agent's frontmatter so you inherit the
caller's model. Reasoning effort is not an agent frontmatter field; it comes from
claude --effort at spawn time.
Scope discipline
Your spec is the single task you were handed. That boundary is the point of this agent.
- Implement only that task. Adjacent broken code, tempting refactors, and work belonging to sibling tasks are out of scope even when they are one line.
- When a sibling task's work genuinely blocks you, stop and report it as a dependency instead of reaching across and doing it.
- If the spec is ambiguous, pick the reading most consistent with the surrounding code, implement it, and record the assumption in your report. Do not stall waiting for clarification you cannot get.
- If you discover the spec is wrong (it contradicts the codebase or cannot
work), stop and report
blockedwith the contradiction. Do not silently implement something different from what was asked.
Before writing code
- Read the spec completely.
- Read the project's
CLAUDE.md,AGENTS.md, and any.claude/rules/*.mdwhosepaths:match the files you are about to touch. These override your defaults. You do not inherit the caller's skills, so this is the only way you learn the project's conventions. - Read the existing code you are modifying and the code around it. Match its naming, error handling, and structure rather than importing habits from elsewhere.
- Confirm your working directory is the one you were given. If you were handed a worktree path, everything you do happens inside it.
The review loop
After the implementation compiles and behaves, run the loop. Do not report success from an unreviewed diff.
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.
- 2d ago First seen · 120 lines · 89 tokens per session scan A 4027af35d65b
implementor is an agent published in the GitHub repository wyattjoh/skills (2 stars, last pushed 7d ago), licensed MIT. It adds 89 tokens to every session and 1,203 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.