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 ToruAI/toru-claude-agents --skill claude-code-masterygit clone --depth 1 https://github.com/ToruAI/toru-claude-agentsWrote 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/toruai/toru-claude-agents/claude-code-mastery)<a href="https://agentmods.dev/skills/toruai/toru-claude-agents/claude-code-mastery"><img src="https://agentmods.dev/badge/skills/toruai/toru-claude-agents/claude-code-mastery/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/toruai/toru-claude-agents/claude-code-mastery"><img src="https://agentmods.dev/badge/skills/toruai/toru-claude-agents/claude-code-mastery.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.00027 | $0.01143 |
| Opus 5 | $0.00014 | $0.00571 |
| Sonnet 5 | $0.00005 | $0.00229 |
| Haiku 4.5 | $0.00003 | $0.00114 |
Grade A, and why
claude-code-mastery 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 9d 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Mastery - Building Better AI Systems
Use the cc-docs skill to read the official Claude Code documentation before you design
anything against it — the spec moves, and this file is a map, not a substitute for it.
Use this knowledge to continuously improve how you work.
Core Capabilities
Subagents
Location: ~/.claude/agents/ (user) or .claude/agents/ (project)
Key fields:
---
name: agent-name
description: When Claude should delegate here
tools: Read, Grep, Glob, Bash, Edit, Write
model: sonnet | opus | haiku | inherit
permissionMode: default | acceptEdits | bypassPermissions
skills: skill-1, skill-2
hooks:
PreToolUse: [...]
PostToolUse: [...]
---
System prompt content here...
Use subagents when:
- Task needs isolated context
- Different tools/permissions needed
- Specialized behavior required
Skills
Location: ~/.claude/skills/ (user) or .claude/skills/ (project)
Structure:
skill-name/
├── SKILL.md # Required - main instructions
├── reference.md # Optional - detailed docs
└── scripts/ # Optional - utilities
Key fields:
---
name: skill-name
description: When to apply this skill (triggers auto-loading)
allowed-tools: Read, Grep, Glob # Optional tool restriction
context: fork # Optional - run in subagent
---
Instructions here...
Use skills when:
- Knowledge should auto-apply based on task
- Pattern repeats across projects
- Want to inject expertise without delegation
Hooks
Location: .claude/settings.json or subagent frontmatter
Events:
PreToolUse- Before tool executes (can block)PostToolUse- After tool executesSubagentStart- When subagent beginsSubagentStop- When subagent completesSessionStart- When session begins
Example:
{
"hooks": {
"PostToolUse": [{
"matcher": "Edit|Write",
"hooks": [{
"type": "command",
"command": "./scripts/auto-lint.sh"
}]
}]
}
}
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.
- 9d ago First seen · 175 lines · 27 tokens per session scan A a86da1760a90
claude-code-mastery is a skill published in the GitHub repository ToruAI/toru-claude-agents (15 stars, last pushed 1mo ago), licensed MIT. It adds 27 tokens to every session and 1,143 once invoked, about $0.0001 per session on Opus 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-08-30.
Other skills, from other repositories
ln-11-plan-reviewer
Reviews an implementation plan against repository evidence before execution; identifies missing decisions and risks. Not for completed-code review.
ln-12-delivery-reviewer
Reviews a completed change for regressions, unmet acceptance, and release risks. Not for whole-codebase audits or repairs.
ln-22-codebase-auditor
Audits cross-cutting code health, security, delivery, and maintainability when no specialist audit is primary. Not for a single delivery review.
ln-23-test-suite-auditor
Audits existing tests for meaningful coverage, trustworthy oracles, and maintenance value. Not for test implementation or a single delivery review.
ln-21-documentation-auditor
Audits documentation and comments for trustworthy claims, coverage, and discoverability. Not for code, test, or architecture audits.
ln-24-architecture-auditor
Audits implemented architecture, boundaries, dependencies, and configuration ownership. Not for documenting current state or reviewing plans.