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/emdashcodes/claude-code-plugins/claude-code-hooksnpx skills add emdashcodes/claude-code-plugins --skill claude-code-hooksgit clone --depth 1 https://github.com/emdashcodes/claude-code-pluginsWhat 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.00054 | $0.02791 |
| Opus 5 | $0.00027 | $0.01396 |
| Sonnet 5 | $0.00011 | $0.00558 |
| Haiku 4.5 | $0.00005 | $0.00279 |
Grade D, and why
claude-code-hooks scanned grade D with 2 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 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.
**User hooks:** `~/.claude/settings.json` - Personal preferences, cross-project automation Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
- "Should the hook allow sudo/rm -rf commands, or block them entirely?" How it starts
The opening of the file, as written. The whole thing — 371 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claude Code Hooks
This skill provides assistance for working with Claude Code hooks to enable automation of workflows and integration of external tools through an event-driven system.
About Hooks
Hooks are event-driven automation scripts that execute automatically when specific events occur during Claude Code's operation. Think of them as "middleware" for Claude's actions—they intercept events to validate inputs, enrich context, automate workflows, or integrate external tools, transforming Claude from a general assistant into a policy-aware, context-enriched agent.
What Hooks Provide
- Input validation - Block dangerous operations, enforce security policies, prevent path traversal
- Workflow automation - Auto-format code, run linters, backup files, send notifications
- Context enrichment - Load git status, inject project context, add session information
- External integration - Connect to APIs, trigger CI/CD, log to external systems
- Decision control - Auto-approve safe operations, require confirmation for sensitive actions
Anatomy of a Hook
Every hook consists of configuration in settings.json and an optional validation script:
.claude/
├── settings.json - Hook configuration (required)
│ └── hooks:
│ └── EventName: - Which event to hook (PreToolUse, PostToolUse, etc.)
│ └── matcher: - Which tools to match (regex pattern)
│ └── command: - What to execute (shell command or script)
└── hooks/ - Hook scripts (optional)
└── script-name.py - Validation/automation logic
Configuration (required)
Hooks are configured in settings.json with event type, tool matcher, and command:
{
"hooks": {
"PreToolUse": [
{
"matcher": "Bash",
"hooks": [
{
"type": "command",
"command": "${CLAUDE_PROJECT_DIR}/.claude/hooks/validate-bash.py",
"timeout": 60
}
]
}
]
}
}
What ships with it
3 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.
- 2d ago First seen · 371 lines · 54 tokens per session scan D e67c13d26f2e
claude-code-hooks is a skill published in the GitHub repository emdashcodes/claude-code-plugins (13 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 2,791 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it D with 2 findings (reads agent configuration directories, recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
weekly-digests
Generate a serial week-by-week narrative digest of a project's full claude-mem timeline. Splits the timeline into per-ISO-week files, then runs one consecutive subagent per week — each receiving the prior week's carry-forward block — to produce one chapter per ISO week of data. Use when asked for "weekly digests"…
agentmail
Use when an agent needs AgentMail CLI email inboxes.
skill-template
Template for creating new Agent Skills for context engineering. Use this template when adding new skills to the collection.
Agent Development
This skill should be used when the user asks to "create an agent", "add an agent", "write a subagent", "agent frontmatter", "when to use description", "agent examples", "agent tools", "agent colors", "autonomous agent", or needs guidance on agent structure, system prompts, triggering conditions, or agent development…
skill-creator
Scaffold a new yoyo skill when a human or community issue asks for one ("add a skill for X", "create a skill that does Y"). Generates correct frontmatter, validates, writes to disk.
subagent-delegation
Canonical protocol for delegating GSD work to native Antigravity subagents — when to delegate, how to invoke, workspace isolation modes, and the inline fallback for older IDE versions.