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 skills/bendrucker/claude/hooknpx skills add bendrucker/claude --skill hookgit clone --depth 1 https://github.com/bendrucker/claudeWhat 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.00084 | $0.01361 |
| Opus 5 | $0.00042 | $0.00681 |
| Sonnet 5 | $0.00017 | $0.00272 |
| Haiku 4.5 | $0.00008 | $0.00136 |
Grade B, and why
claude-code:hook scanned grade B 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 2d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- `~/.claude/settings.json` - User-level (global) How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Hooks
Reference for creating and configuring Claude Code hooks. When uncertain about syntax or features, use the Agent tool with subagent_type='claude-code-guide' to consult official docs.
Hook Types
| Type | Trigger | Use Cases |
|---|---|---|
| PreToolUse | Before tool execution | Validate inputs, block operations, modify parameters |
| PostToolUse | After tool completes | Check results, run linters, provide feedback |
| UserPromptSubmit | When user sends message | Pre-process input, add context |
| PermissionRequest | Permission dialog appears | Return a decision, notify a remote approver |
| Stop | Agent finishes a turn | Cleanup, save state |
| StopFailure | Agent stops on failure | Report the failure |
| SubagentStart / SubagentStop | Subagent spawns / completes | Process results |
| SessionStart / SessionEnd | Session begins / ends | Inject context, export state |
| PreCompact / PostCompact | Around context compaction | Save important state |
| Notification | System notification | Log events |
| TeammateIdle | Teammate about to go idle | Hand off work |
Configuration Files
~/.claude/settings.json- User-level (global).claude/settings.json- Project-level.claude/settings.local.json- Local (not committed)- Plugin hooks:
plugins/<name>/hooks/hooks.json
Hook Structure
{
"hooks": {
"PostToolUse": [
{
"matcher": "Edit|Write",
"hooks": [
{
"type": "command",
"command": "bun ./hooks/ox"
}
]
}
]
}
}
Matcher Patterns
- Simple:
"Write","Edit" - Multiple:
"Edit|Write|MultiEdit" - With args:
"Bash(npm:*)","Bash(osascript:*)|Bash(open:*)" - MCP tools:
"mcp__linear__create_issue" - Plugin MCP tools:
"mcp__plugin_<plugin>_<namespace>__<tool>" - Claude AI MCP tools:
"mcp__claude_ai_<DisplayName>__<tool>" - All three patterns:
"mcp__linear__create_issue|mcp__plugin_linear_linear__create_issue|mcp__claude_ai_Linear__save_issue"
What ships with it
1 file 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.
- 2d ago First seen · 145 lines · 84 tokens per session scan B c2c5bf56056c
claude-code:hook is a skill published in the GitHub repository bendrucker/claude (16 stars, last pushed 2d ago), licensed MIT. It adds 84 tokens to every session and 1,361 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.