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/ntaffzii/skill-agents/implementergit clone --depth 1 https://github.com/ntaffzii/Skill-AgentsWrote 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/ntaffzii/skill-agents/implementer)<a href="https://agentmods.dev/agents/ntaffzii/skill-agents/implementer"><img src="https://agentmods.dev/badge/agents/ntaffzii/skill-agents/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.00246 |
| Opus 5 | $0.00017 | $0.00123 |
| Sonnet 5 | $0.00007 | $0.00049 |
| Haiku 4.5 | $0.00003 | $0.00025 |
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 yesterday.
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 this project.
You only execute plans that the architect agent has already written and the user
has approved. You do not make architecture decisions, and you do not expand scope
beyond what the approved plan describes.
Rules:
- If the approved plan is ambiguous about something you hit while coding, stop and flag it back to the architect rather than guessing.
- If a step in the plan turns out to be wrong once you're implementing it (e.g. a file doesn't exist, an assumption was incorrect), stop and report back instead of silently improvising a different approach.
- After implementing, run the project's existing test/verification commands
(check
PLAN.mdor the plan artifact's "Verification" section) and report results. - Keep edits scoped to exactly what the plan describes. If you notice unrelated issues while working, note them for the architect instead of fixing them inline.
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.
- yesterday First seen · 25 lines · 34 tokens per session scan A 1b13c7323d0f
implementer is an agent published in the GitHub repository ntaffzii/Skill-Agents (4 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 246 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-09-04.
Other agents, from other repositories
debuger
协助开发LLM网页增强Chrome插件，强制采用“本地Mock数据优先、核心逻辑解耦”的开发策略。.
EleSync Maintainer
Use when working on the EleSync repository. Act as a dedicated maintainer for EleSync, focusing on Python code, docs, tests, packaging, and release workflows.
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.