Claude Code Ultimate Guide is a structured documentation project for learning how to build, operate, and govern coding agents with Claude Code. It serves developers and teams through guidance on agentic workflows, hooks, skills, MCP servers, security, and adoption. The catalogue entries are reusable skills, commands, agents, hooks, instructions, settings, and a plugin drawn from the guide's workflow materials.
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 FlorianBruniaux/claude-code-ultimate-guide --skill git-worktree-statusgit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-ultimate-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/florianbruniaux/claude-code-ultimate-guide/git-worktree-status)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-ultimate-guide/git-worktree-status"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-ultimate-guide/git-worktree-status/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/florianbruniaux/claude-code-ultimate-guide/git-worktree-status"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-ultimate-guide/git-worktree-status.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.00017 | $0.01264 |
| Opus 5.5 | $0.00007 | $0.00506 |
| Sonnet 5.5 | $0.00003 | $0.00253 |
| Haiku 4.5 | $0.00002 | $0.00126 |
Grade C, and why
git-worktree-status scanned grade C with 1 finding 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 16d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf .worktree-logs/*.log The source is not reproduced here
Licensed CC-BY-SA-4.0
The repository is licensed CC-BY-SA-4.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.
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.
- 16d ago Changed 06f6b14e897f
- 1mo ago First seen · 167 lines · 17 tokens per session scan C 5ba52c7fb0bb
git-worktree-status is a skill published in the GitHub repository FlorianBruniaux/claude-code-ultimate-guide (6,191 stars, last pushed yesterday), licensed CC-BY-SA-4.0. It adds 17 tokens to every session and 1,264 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
git
Git version control best practices: branching, commits, merging, conflict resolution, PR workflows. Use when managing branches, creating commits, merging code, or resolving conflicts.
code-review-loop
Use when opening a PR for review or when receiving review feedback. Activate for keywords like "code review", "PR review", "request review", "review feedback", "address comments", "reviewer said". Covers both ends of the loop: preparing a reviewable PR and acting on feedback rigorously. Always engage with every…
release-and-changelog
Use when cutting a release, bumping a version, or writing release notes. Activate for keywords like "release", "version bump", "changelog", "release notes", "tag", "publish", "ship a release", "v1.x", "v2.x". Enforces version hygiene: SemVer respect, changelog discipline, atomic commits, tagged release. Always reflect…
devops
DevOps patterns: containerization, CI/CD, deployment strategies, monitoring. Use when containerizing apps, setting up pipelines, or deploying services.
learning
Extracts reusable patterns from sessions. Use at session end to capture debugging insights and project-specific knowledge.
api
RESTful API design patterns and best practices. Use when creating endpoints, designing APIs, or implementing routes.