Claude Code Guide is a reference collection for configuring and using Claude Code, Anthropic’s command-line coding agent. Developers use it to learn commands, skills, agents, MCP, automation, security, integrations, and troubleshooting. Its catalogue add-ons provide many of the documented skills and agents.
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.
git clone --depth 1 https://github.com/zebbern/claude-code-guideWrote 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/zebbern/claude-code-guide/change-implementer)<a href="https://agentmods.dev/agents/zebbern/claude-code-guide/change-implementer"><img src="https://agentmods.dev/badge/agents/zebbern/claude-code-guide/change-implementer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/zebbern/claude-code-guide/change-implementer"><img src="https://agentmods.dev/badge/agents/zebbern/claude-code-guide/change-implementer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00047 | $0.00435 |
| Opus 5.5 | $0.00019 | $0.00174 |
| Sonnet 5.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 1mo 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.
- 1mo 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,667 stars, last pushed yesterday), licensed MIT. It adds 47 tokens to every session and 435 once invoked, about $0.0002 per session on Opus 5.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
self-review-cold-grader
Reviewer for angle X of the self-review loop. Grades the transcript of a cold run that already happened inside containment; has no shell and executes nothing. Spawned by the self-review skill with an intent statement, a scope file and a transcript path; returns candidate findings as JSON.
self-review-finder
Read-only reviewer for one angle of the self-review loop. Spawned by the self-review skill with an intent statement, a scope file, one review angle, and the dismissed ledger; returns candidate findings as JSON. Never edits files.
self-review-verifier
Read-only adversarial verifier for the self-review loop. Takes one or more candidate findings plus the scope file and returns a CONFIRMED / PLAUSIBLE / REFUTED verdict with quoted proof for each. Never edits files.
self-review-applier
The writing hand of the self-review loop. Applies one round's fix directives to the working tree, in order, exactly as written, and reports applied / deviated / blocked per directive as JSON. Spawned by the self-review skill (or its orchestrator), one per round, with a directives file. Has no shell — it cannot run…
self-review-ticket-validator
Reads the INTENT block once, before any code is written, and rules on the ticket rather than on the change. Spawned by the ticket skill with the user's request and the intent file; returns sound / revise / do-not-build as JSON, with a corrected INTENT block when it revises. Read-only.
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.