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 agentmods add commands/florianbruniaux/claude-code-ultimate-guide/generate-testsgit 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/commands/florianbruniaux/claude-code-ultimate-guide/generate-tests)<a href="https://agentmods.dev/commands/florianbruniaux/claude-code-ultimate-guide/generate-tests"><img src="https://agentmods.dev/badge/commands/florianbruniaux/claude-code-ultimate-guide/generate-tests.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00069 |
| Opus 5 | $0.00000 | $0.00034 |
| Sonnet 5 | $0.00000 | $0.00014 |
| Haiku 4.5 | $0.00000 | $0.00007 |
Grade A, and why
generate-tests 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 yesterday.
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.
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.
- yesterday First seen · 6 lines · 0 tokens per session scan A 6e5b1eb81cef
generate-tests is a command published in the GitHub repository FlorianBruniaux/claude-code-ultimate-guide (5,899 stars, last pushed today), licensed CC-BY-SA-4.0. It costs nothing until one of its globs matches a file; then it loads 69 tokens. 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 commands, from other repositories
implementar
Ejecutar tareas TDD fase por fase dentro de Docker hasta que todos los tests pasen.
merge-work-packets
Verify all tracks complete, invoke merging-worktrees, run QA gates, report final integration status.
merge-worktree-execute
Phase 2: Sequential Round Merging - merge worktrees in dependency order with testing after each round.
designer
作为 UI/UE 设计师，负责界面设计审查和用户体验优化。核心能力是将技术方案转化为美观、独特、有记忆点的界面设计，确保产品的视觉质量和用户体验，避免"AI slop"通用审美。.
evolve
将积累的学习内容聚类分析，演化为更高级的结构：Skills、Agents 或 Commands。核心原则：量变引发质变，经验升华为能力。.
validate
You are the quality gate. Your job is to verify that a phase's implementation meets quality standards before the team moves to the next phase. No phase should advance until validation passes.