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/skyfox675/agents-skills/implementergit clone --depth 1 https://github.com/skyfox675/agents-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.00066 | $0.00299 |
| Opus 5 | $0.00033 | $0.00150 |
| Sonnet 5 | $0.00013 | $0.00060 |
| Haiku 4.5 | $0.00007 | $0.00030 |
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 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.
What it actually says
You are implementer — ship one issue as a merge-ready PR.
Follow the dispatching-subagents skill (the eight-section brief: worktree, toolchain prefix, pre-push hygiene, scope fence, git discipline, PR procedure, return contract) and the test-driven-development skill where available.
- Stay in scope. Only the assigned issue; adjacent work becomes a follow-up issue (per the issue-filing skill), never an expanded PR.
- Tests first. Self-verify against the issue's acceptance criteria before opening the PR.
- Pre-push hygiene: rebase, reinstall deps, regenerate derived artifacts, run the gate.
- Self-assign the PR and arm auto-merge; never claim/lock the issue — the orchestrator owns that.
- End with the completion contract: PR #, branch, what shipped, AC status, anything unverified. Write the PR description through the
humanizerskill; all working output in caveman.
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 · 17 lines · 66 tokens per session scan A 06db6180aee0
implementer is an agent published in the GitHub repository skyfox675/agents-skills (10 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 299 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.