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/dixus/claudeframework/create-hooknpx skills add dixus/claudeframework --skill create-hookgit clone --depth 1 https://github.com/dixus/claudeframeworkWhat 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.00035 | $0.02428 |
| Opus 5 | $0.00017 | $0.01214 |
| Sonnet 5 | $0.00007 | $0.00486 |
| Haiku 4.5 | $0.00003 | $0.00243 |
Grade B, and why
create-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.
- Global scope: `~/.claude/settings.json` How it starts
The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyse the project, suggest useful hooks, then create and validate the one the user selects.
$ARGUMENTS is optional — pass a description of what you want the hook to do (e.g. "type-check after every edit") to skip the suggestion step.
Step 1 — Detect tooling and suggest hooks
Scan the project root for these indicators and propose relevant hooks:
| Detected | Suggested hook |
|---|---|
tsconfig.json |
PostToolUse — type-check .ts/.tsx files after each edit; surface errors as additionalContext so Claude auto-fixes |
.prettierrc / prettier.config.* |
PostToolUse — auto-format the edited file after each Write/Edit |
.eslintrc.* / eslint.config.* |
PostToolUse — lint + auto-fix the edited file after each Write/Edit |
package.json with test script |
PreToolUse (Bash) — run tests before any git commit command |
.git/ directory |
PreToolUse (Bash) — scan staged files for secrets/API keys before commit |
| Any project | PostToolUse — block writes to protected directories (migrations/, generated/) |
If $ARGUMENTS was provided, skip suggestions and go directly to Step 2 using the described purpose.
Otherwise: list the suggested hooks and ask the user which one to create. If they describe a custom purpose, proceed with that.
Step 2 — Configure the hook
Ask only what you don't already know from the user's description:
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 · 248 lines · 35 tokens per session scan B 1b255e188c7e
create-hook is a skill published in the GitHub repository dixus/claudeframework (10 stars, last pushed 4mo ago), licensed MIT. It adds 35 tokens to every session and 2,428 once invoked, about $0.0002 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-31.
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.
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.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…