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.
npx skills add zebbern/claude-code-guide --skill repo-auditgit 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/skills/zebbern/claude-code-guide/repo-audit)<a href="https://agentmods.dev/skills/zebbern/claude-code-guide/repo-audit"><img src="https://agentmods.dev/badge/skills/zebbern/claude-code-guide/repo-audit/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/skills/zebbern/claude-code-guide/repo-audit"><img src="https://agentmods.dev/badge/skills/zebbern/claude-code-guide/repo-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.00809 |
| Opus 5.5 | $0.00024 | $0.00324 |
| Sonnet 5.5 | $0.00012 | $0.00162 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
repo-audit 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.
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repo Audit — Deep Analysis of Git History
Perform three-dimensional analysis on a Git repository: hotspot file detection, code ownership analysis, and secret leak scanning.
Feature Overview
1. Hotspot File Analysis (scripts/hotfiles.sh)
Identify the most frequently changed files in a repository to help spot:
- High-risk code areas (frequent changes = potential instability)
- Files that deserve extra attention during code review
- Modules that may need splitting or refactoring
Usage:
bash scripts/hotfiles.sh [options]
| Option | Description | Default |
|---|---|---|
--repo PATH |
Repository path | Current directory |
--top N |
Show top N files | 20 |
--since DATE |
Start date (e.g. 2024-01-01) |
None |
--until DATE |
End date | None |
--author AUTHOR |
Filter by author | None |
--format FORMAT |
Output format: table / csv / json |
table |
2. Code Ownership Analysis (scripts/ownership.sh)
Analyze actual code ownership, reporting for each contributor within the specified scope:
- Commit count and percentage
- Lines changed (additions/deletions)
- Last active date
Usage:
bash scripts/ownership.sh [options]
| Option | Description | Default |
|---|---|---|
--repo PATH |
Repository path | Current directory |
--path SUBPATH |
Analyze a specific subdirectory or file | Entire repo |
--top N |
Show top N contributors | 10 |
--since DATE |
Start date | None |
--format FORMAT |
Output format: table / csv / json |
table |
3. Secret Leak Scanning (scripts/secret-scan.sh)
Scan the full Git history (including deleted commits) for common secrets and sensitive information:
- AWS Access Key / Secret Key
- GitHub / GitLab / Slack Tokens
- SSH Private Keys
- Generic API Keys, passwords, and secret patterns
Usage:
bash scripts/secret-scan.sh [options]
| Option | Description | Default |
|---|---|---|
--repo PATH |
Repository path | Current directory |
--branch BRANCH |
Scan a specific branch | All branches |
--since DATE |
Start date | None |
--format FORMAT |
Output format: table / csv / json |
table |
--severity LEVEL |
Minimum severity level: low / medium / high |
low |
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 95 lines · 60 tokens per session scan A 978d00c620f6
repo-audit is a skill published in the GitHub repository zebbern/claude-code-guide (4,677 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 809 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-09-03.
Other skills, from other repositories
catchup
Answer "where did I stop?" for this project. Gives three short groups, done, open and next, taken from the last chat, the recorded to-dos, the last handoff note and git. Use when the user comes back to a project, starts a new chat, or asks where they left off. It writes nothing.
git-commit
Analyze changes with Git only and auto-generate conventional commit messages with optional emoji; suggests splitting commits when needed, runs local Git hooks by default (use --no-verify to skip).
core-workflow
Detailed development workflow patterns, checklists, and standards. Auto-loads for complex tasks, planning, debugging, or when explicit patterns are needed. Contains session protocols, git conventions, security checklists, review-based validation, and communication standards.
pr-review
Review pull requests and Git diffs with Graph-It-Live risk, breaking-change, dependency-impact, cycle, unused-export, and test-candidate evidence. Use when asked to review a PR, inspect a diff, assess merge risk, check a branch before merging, create a Graph-It-Live review gate, or explain review-pr results. Trigger…
ops-standup
Cross-repo morning briefing. Aggregation of recent commits, PRs, CI, blockers and priorities of the day. Trigger when the user wants a standup, an activity summary, or to know what happened.
work-batch
Sequential execution of user stories from a PRD file. Autonomous mode that implements and commits each story one by one. Trigger when the user wants to process a backlog, execute multiple stories, or launch an autonomous mode.