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/tsmztech/claude-code-plugins/create-hooknpx skills add tsmztech/claude-code-plugins --skill create-hookgit clone --depth 1 https://github.com/tsmztech/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.00041 | $0.00489 |
| Opus 5 | $0.00020 | $0.00244 |
| Sonnet 5 | $0.00008 | $0.00098 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
create-hook scanned grade A 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 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.
Reads agent configuration directorieslowAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Path given → add to `<path>/.claude/settings.json` (project, shareable) or `<path>/.claude/settings.local.json` (project, gitignored) Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
What it actually says
Create a Claude Code Hook
Read first: ${CLAUDE_PLUGIN_ROOT}/docs/hooks-guide.md — this is the full reference for hook events, matchers, input/output formats, hook types, and examples. Use it to guide every decision.
Determine target location
Hooks live in JSON settings files, not standalone files. Check if the user passed a path as $ARGUMENTS.
- Path given → add to
<path>/.claude/settings.json(project, shareable) or<path>/.claude/settings.local.json(project, gitignored) personal→ add to~/.claude/settings.json(all projects)- Nothing → ask where. Explain the scoping options (see "Configure hook location" in the doc)
Plugin note: If the user is creating a hook for a plugin, hooks go in hooks/hooks.json at the plugin root — not in settings.json. The format is the same. See "Migrate hooks" in the plugins doc (${CLAUDE_PLUGIN_ROOT}/docs/plugins.md).
Gather requirements
Ask the user what they want to automate. From their answer, use the doc to determine:
- Which event to hook into (see the event table in "How hooks work")
- Whether a matcher is needed to narrow when it fires (see "Filter hooks with matchers")
- Which hook type fits —
commandfor shell scripts,promptfor LLM judgment,agentfor multi-turn verification (see respective sections in the doc) - What the hook should output (exit codes, JSON, stderr — see "Read input and return output")
Create the hook
Read the existing settings file at the target location first — merge the new hook into the existing hooks object without clobbering other settings or hooks. If the file doesn't exist, create it with just the hooks config.
If the hook needs an external script, create it alongside and make it executable.
After creating, tell the user how to test it.
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 · 37 lines · 41 tokens per session scan A 381651535932
create-hook is a skill published in the GitHub repository tsmztech/claude-code-plugins (2 stars, last pushed 6mo ago), licensed MIT. It adds 41 tokens to every session and 489 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…