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 eval-rulesgit 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/eval-rules)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-ultimate-guide/eval-rules"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-ultimate-guide/eval-rules/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/eval-rules"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-ultimate-guide/eval-rules.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.00082 | $0.03547 |
| Opus 5.5 | $0.00033 | $0.01419 |
| Sonnet 5.5 | $0.00016 | $0.00709 |
| Haiku 4.5 | $0.00008 | $0.00355 |
Grade A, and why
eval-rules scanned grade A 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 20d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
git = subprocess.run(["git", "-C", root, "ls-files", "-co", "--exclude-standard"], capture_output=True, text=True) 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.
- 20d ago Changed 4e4ce502f34f
- 22d ago Changed · -1 lines · -2 tokens per session fb8879467544
- 1mo ago First seen · 226 lines · 84 tokens per session scan A 0f13fe736dac
eval-rules is a skill published in the GitHub repository FlorianBruniaux/claude-code-ultimate-guide (6,218 stars, last pushed today), licensed CC-BY-SA-4.0. It adds 82 tokens to every session and 3,547 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
second-opinion
Cross-validate code, architecture or design decisions using a second model. Use for critical decisions, complex refactoring, security reviews.
code-review
A code-review procedure for checking whether changes meet their requirements, behave correctly, stay within safe boundaries, and have effective tests.
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…
aio-review-deep
Deep multi-agent code review — dispatch a fleet of parallel specialized agents (security, architecture, quality, performance) with GitNexus domain analysis. Use before merging a PR or after a major feature lands when a single-pass review is too shallow. For a quick pre-commit sanity check use aio-review-quick.
aio-map
Trace dependencies, call graphs, and blast radius for a file/function/module via GitNexus + LSP. Step 2 of the codeflow discover → map → plan trio (after aio-discover, before aio-plan).
devops
DevOps patterns: containerization, CI/CD, deployment strategies, monitoring. Use when containerizing apps, setting up pipelines, or deploying services.