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 xonovex/platform --skill claude-code-guidegit clone --depth 1 https://github.com/xonovex/platformWrote 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/xonovex/platform/claude-code-guide)<a href="https://agentmods.dev/skills/xonovex/platform/claude-code-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/claude-code-guide/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/xonovex/platform/claude-code-guide"><img src="https://agentmods.dev/badge/skills/xonovex/platform/claude-code-guide.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.00086 | $0.00561 |
| Opus 5.5 | $0.00034 | $0.00224 |
| Sonnet 5.5 | $0.00017 | $0.00112 |
| Haiku 4.5 | $0.00009 | $0.00056 |
Grade A, and why
claude-code-guide 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Hooks
Configure Claude Code's native hook and extension surface without inventing unsupported guarantees or a universal hook format.
Essentials
- Pin the surface - Record the documentation snapshot and observed
claude --versionresult before selecting a guarantee. - Map event semantics - Translate requested behavior through the versioned capability matrix, never by event-name similarity.
- Preserve handler differences - Command, HTTP, MCP-tool, prompt, and agent handlers have event-specific support and output behavior.
- Assume parallel matching - Make handlers reentrant and do not expect a denial to cancel sibling side effects.
- Respect settings authority - Managed, user, project, local, plugin, and component hooks have native precedence and trust rules.
- Onboard transactionally - Preview exact settings/plugin changes, permissions, data flow, verification, disable, and rollback before apply.
- Keep hooks focused - Give each handler one native event contract and one explicit responsibility.
Gotchas
- Agent handlers are experimental; do not select them when the requested control requires a verified blocking guarantee.
- Exit code
2is the blocking signal for most blocking events; exit code1is normally a non-blocking error. - There is no standalone
.claude/hooks.json; standalone hooks live under thehookskey in a settings file. - All matching handlers run in parallel, so a blocking result does not undo a sibling handler that already produced a side effect.
- Managed settings may restrict hook sources, but executable distribution and provenance remain separate.
Example
A project can use a deterministic PreToolUse command to inspect covered tool calls and return Claude Code's documented blocking response when its explicit rule rejects one.
Progressive Disclosure
- Read references/capabilities.md - Load when mapping semantic intents to native events, handlers, guarantees, versions, ordering, context, or limitations
- Read references/onboarding.md - Load when discovering, previewing, applying, verifying, disabling, rolling back, updating, or detecting drift
- Read references/patterns.md - Load when translating deterministic hooks, model evaluators, specialist agents, or managed adoption recipes
What ships with it
7 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 · 37 lines · 86 tokens per session scan A 1b201be9b514
claude-code-guide is a skill published in the GitHub repository xonovex/platform (6 stars, last pushed 2d ago), licensed MIT. It adds 86 tokens to every session and 561 once invoked, about $0.0003 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-08.
Other skills, from other repositories
harbor-daytona
Use Harbor's Daytona sandbox platform for computer use — creating sandboxes, taking screenshots, sending mouse/keyboard input, and building agent loops. Use when the user wants to interact with a GUI, automate a desktop, do computer use, control a browser visually, or run Claude computer use against a Daytona sandbox.
docker
Use when authoring or auditing a Dockerfile, shrinking a bloated image, hardening a container that runs as root, picking a base image, or wiring a Compose dev loop with hot reload. NOT CI builds or deploy-to-host (that is deployment), NOT k8s autoscaling (that is scaling), NOT app-level injection or secrets-in-code…
kastell
Server security auditing, hardening, and fleet management. 457 security checks across 30 categories (SSH, Firewall, Docker, TLS, HTTP Headers), CIS/PCI-DSS/HIPAA compliance mapping, 24-step production hardening, and 13 MCP tools. Supports Hetzner, DigitalOcean, Vultr, and Linode with Coolify, Dokploy, and bare VPS…
ilo
Run builds, tests, and other tooling inside a reproducible, containerized dev environment via the ilo CLI instead of on the host. Use this whenever a project relies on ilo, devcontainers, or container-based build environments — it has a .ilo.rc / .ilo/ilo.rc, dev/ argument files, a Containerfile/Dockerfile, a…
docker-compose-local-setup
Creates or updates local multi-service orchestration using docker compose. Covers compose.yaml design, service health checks, dependson readiness, env files, named volumes, migrations/seeds jobs, verification commands, and cleanup workflows for local development.
compose
A guide to Docker Compose, a tool for defining and running applications made of multiple containers, such as a web app, API, and database.