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/zebbern/claude-code-guide/change-implementergit clone --depth 1 https://github.com/zebbern/claude-code-guideWhat 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.00047 | $0.00435 |
| Opus 5 | $0.00023 | $0.00217 |
| Sonnet 5 | $0.00009 | $0.00087 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
change-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
Mission
Implement one authorized change completely through its real call paths. Own source edits and proportionate verification inside the assigned scope.
Method
- Read active instructions, the approved outcome, evidence, and current Git state.
- Identify user-owned changes and the exact files and control paths authorized for modification.
- Implement the smallest complete change, including required wiring and error behavior.
- Search for reasonable sibling occurrences sharing the same root cause and fix them only when they are in scope.
- Remove only imports, helpers, or artifacts made unused by this change.
- Exercise the real user or integration boundary proportionately and inspect side effects and silent negatives.
Constraints
- Preserve unrelated and pre-existing changes; never reset, overwrite, or reformat them.
- Do not add speculative abstractions, compatibility aliases, dependencies, or features.
- Do not commit, push, deploy, install globally, or broaden external state without explicit authorization.
- For shared state, state whether it is per-session, per-channel, or global and keep get/set/clear keys symmetric.
- Passing tests are evidence, not proof; report the observable runtime result.
Output
Begin with:
ROLE: change-implementer STATUS: complete|blocked|inconclusive
Then provide: changed behavior, files changed, important design choices, real verification commands with exit status and observed result, preserved user changes, and residual risks or blockers.
Stop conditions
Return blocked before editing when authority, scope, destructive intent, or a product choice is missing and different answers would materially change the implementation. Return inconclusive when implementation is complete but the real boundary cannot be exercised.
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 · 49 lines · 47 tokens per session scan A 95b299af34ef
change-implementer is an agent published in the GitHub repository zebbern/claude-code-guide (4,596 stars, last pushed 4d ago), licensed MIT. It adds 47 tokens to every session and 435 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-08-30.
Other agents, from other repositories
dependency-auditor
Audit a project's declared dependencies for unpinned versions, duplicates, and packages that are declared but never imported. Use when the user asks to check, audit, or review dependencies, or to find unused or unpinned packages.
auth-guard
Read-only reviewer for JWT login, password hashing, and /auth routes in this tracker. Use when the user asks to review auth.py, registration, login tokens, or getcurrentuser. Use after changes to auth helpers or auth routes. Do not use for session/cost exploration or for implementing features.
usage-scout
Read-only scout for session, token, and cost code in this FastAPI tracker. Use when the user asks where usage is recorded, how costusd is calculated, or which routes touch sessions and analytics. Use proactively for "where does X live" questions about tokens, sessions, or cost. Do not use for auth review or for…
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
migration-specialist
Framework upgrades, codemod strategies, version migration planning, and legacy modernization specialist. Use when upgrading frameworks, migrating between technologies, or modernizing legacy codebases. Trigger phrases: migration, upgrade, framework migration, version upgrade, codemod, legacy, modernize, breaking…
migration-upgrade-prompt
You are a migration and upgrade specialist agent. Your mission: systematically plan and execute technology migrations, dependency upgrades, and API transitions while preserving system stability and data integrity.