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 sandbox-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/sandbox-status)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-ultimate-guide/sandbox-status"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-ultimate-guide/sandbox-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/sandbox-status"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-ultimate-guide/sandbox-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.00013 | $0.01520 |
| Opus 5.5 | $0.00005 | $0.00608 |
| Sonnet 5.5 | $0.00003 | $0.00304 |
| Haiku 4.5 | $0.00001 | $0.00152 |
Grade C, and why
sandbox-status scanned grade C with 2 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 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
echo " Install: sudo apt-get install bubblewrap socat" Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
elif [ -f ~/.claude/settings.json ]; then 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 987b17b753dd
- 1mo ago First seen · 187 lines · 13 tokens per session scan C 17cca03dd225
sandbox-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 13 tokens to every session and 1,520 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it C with 2 findings (asks for root, reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
debug
Systematic debugging methods, log analysis, and performance diagnostics. Use when debugging issues, analyzing errors, or troubleshooting incidents.
quality
Code quality assurance strategies. Parent skill for quality-related skills: security (security review) and debug (systematic debugging).
five-whys
Finds the root cause of a bug, failure or recurring problem by asking "why" until the answer is a cause you can fix. Use when the user asks why something keeps happening, or wants the root cause rather than a quick fix.
software-health
Assess and maintain software health through scoped change or module reviews, workflow consistency, failure recovery, resource lifetime, performance, and AI instruction/tool contracts when applicable. Use for systematic application-health reviews, contradictory or sluggish behavior across components, and regression…
investigate-root-cause
Use when encountering ANY bug, error, test failure, or unexpected behavior. Activate for keywords like "bug", "error", "failing", "broken", "doesn't work", "unexpected", "crash", "exception", "TypeError", "undefined", stack traces, or any error message. Also trigger when tests fail unexpectedly, when behavior differs…
evidence-driven-debugging
Use during active debugging when you have a hypothesis to test or need to instrument a running system. Activate for keywords like "debug", "instrument", "log", "trace", "breakpoint", "what's happening at runtime", "production behavior". Pair to investigate-root-cause for the doing-it phase. Always record what you…