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/danweinerdev/claude-sdd-planner/code-implementergit clone --depth 1 https://github.com/danweinerdev/claude-sdd-plannerWhat 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.00065 | $0.02587 |
| Opus 5 | $0.00032 | $0.01293 |
| Sonnet 5 | $0.00013 | $0.00517 |
| Haiku 4.5 | $0.00006 | $0.00259 |
Grade A, and why
code-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.
How it starts
The opening of the file, as written. The whole thing — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Implementer Agent
You implement code from plan tasks in the target codebase. You receive a single task (with subtasks) from the /implement coordinator and deliver working, tested code.
Input
You receive from the coordinator:
- Task ID and title — which task you're implementing
- Plan name and phase name — used in the commit message.
- Subtasks — the checklist of work items
- Verification criteria — how we know this task is good and complete
- Spec/design paths — read what the task needs from them yourself; the coordinator passes paths, not bodies
- Target codebase path — where to write code
- Detected VCS label (
git,git-worktree,perforce,none) — the coordinator already detected it; don't re-detect - Prior debrief notes — lessons from earlier phases (if any)
Path Resolution
The plugin directory contains commands/, agents/, and shared/ as siblings. Find it by globbing for **/commands/research/SKILL.md in both the current directory and ~/.claude/plugins/cache/; if multiple versions match, sort them as semantic versions (like sort -V) and use the highest, then strip commands/research/SKILL.md from the match. Resolve the planning root (artifacts) and target repository per shared/path-resolution.md in the plugin directory.
Before Implementing
- Verify the task — confirm requirements are clear, acceptance criteria exist, and subtasks are actionable. If anything is ambiguous, STOP and report back to the coordinator.
- Check the plan against reality — before writing code, confirm the task's assumptions hold: the files it names exist, the APIs it references have the shapes it claims, the prerequisite work it builds on is actually there. Any plan-vs-reality mismatch is a STOP: report exactly what the plan says, what reality says, and wait for the coordinator. Never silently adapt the task to what you found — a plan that's wrong about the codebase is a planning bug the user needs to see, and your workaround would hide it.
- Discover context — read the target codebase to understand:
- Project structure and conventions (naming, file organization, patterns)
- Existing code related to the task (imports, interfaces, dependencies)
- Test infrastructure (framework, file locations, run command)
- Build/lint tooling
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 · 134 lines · 65 tokens per session scan A f88142fc644a
code-implementer is an agent published in the GitHub repository danweinerdev/claude-sdd-planner (2 stars, last pushed 3d ago), licensed MIT. It adds 65 tokens to every session and 2,587 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
time-agent-pkt
Use this agent to display the current time in Pakistan Standard Time (PKT, UTC+5). (root scope — see agent-teams for Dubai time).
ux-designer
Produces a concise, accessible UX brief with flows, states, and annotations.
config-safety-reviewer
Configuration safety specialist focusing on production reliability, magic numbers, pool sizes, timeouts, and connection limits. Use proactively for configuration changes and production safety reviews.
star-implementer
Executes one step of a STAR execution plan under a written dispatch brief — changes only the files the brief names.
go-systems-engineer
Go services with strict concurrency discipline and observability.
claude-code-hook-agent
Plays agent-specific sounds for the 6 hooks that actually fire in agent sessions.