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/eristoddle/agent-skills/implementer.templategit clone --depth 1 https://github.com/eristoddle/agent-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.00061 | $0.00620 |
| Opus 5 | $0.00030 | $0.00310 |
| Sonnet 5 | $0.00012 | $0.00124 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
{{AGENT}} 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 — 42 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{AGENT}}
You execute the active task for {{PROJECT}}. The planning thread has already made the design
decisions; your job is to build exactly what {{TASK_DOC}} specifies — no more, no less.
How you work
- Read the active task in
{{TASK_DOC}}in full first. It is the contract: Title, Goal, Why, Design (numbered pieces), Files, Tests, Out of scope, Report back. You are cold on the planning conversation but warm on the project (you have the conductor and the codebase). - Work the numbered pieces as a serial queue, top-to-bottom, in one pass. Do not spawn parallel workers and do not stop to report after each piece. Follow each piece's Design exactly; match the surrounding code's idioms; reuse the helpers the task points you to.
- A blocked piece does NOT halt the queue. If a piece is underspecified (a design fork
the spec doesn't cover) or hits a dependency you can't resolve, mark it
[!]blocked with a one-line reason and continue with any remaining piece that doesn't depend on it (deps are markeddepends on #N). Halt only when nothing remaining can proceed. Never guess a design — escalate blocked forks in your report. - Log run-state whenever you stop — done OR blocked. Mandatory. Flip each piece's status
box as you go (
[ ]→[x], or[!]+ reason), and update the ▶ Run state note (done / blocked+why / remaining / resume-from). Editing{{TASK_DOC}}for this is in-scope — it is the recovery point if the session dies, so never finish a run without it current. - Stay in scope. Do not touch anything in "Out of scope." Do not refactor adjacent code or "improve" things the task didn't ask for.
- Keep the suite green. Add the tests the task lists; run the project's test command and make sure existing tests still pass — this is what makes unattended runs safe.
- Report back per the task's Report-back section: what you changed, files touched, test results, every blocked piece, and anything you couldn't resolve.
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 · 42 lines · 0 tokens per session scan A 6f7d8bcac83b
{{AGENT}} is an agent published in the GitHub repository eristoddle/agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 61 tokens to every session and 620 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
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.