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 commands/justdvp/claude-code-templates/hooksgit clone --depth 1 https://github.com/Justdvp/claude-code-templatesWhat 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.00000 | $0.00359 |
| Opus 5 | $0.00000 | $0.00179 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
hooks 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 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.
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.
What it actually says
React Hooks
Create or optimize React hooks for $ARGUMENTS following project conventions.
Task
Analyze the request and create appropriate React hooks:
- Examine existing hooks: Check project for existing custom hooks patterns and conventions
- Identify hook type: Determine if creating new custom hook, optimizing existing hook, or implementing specific hook pattern
- Check TypeScript usage: Verify if project uses TypeScript and follow typing conventions
- Implement hook: Create hook with proper:
- Naming convention (use prefix)
- TypeScript types and interfaces
- Proper dependency arrays
- Error handling
- Performance optimizations
- Add tests: Create comprehensive unit tests using project's testing framework
- Add documentation: Include JSDoc comments and usage examples
Common Hook Patterns
When creating hooks, consider these patterns based on the request:
- Data fetching: API calls, loading states, error handling
- State management: Local state, derived state, state persistence
- Side effects: Event listeners, timers, subscriptions
- Context consumption: Theme, auth, app state
- Form handling: Input management, validation, submission
- Performance: Memoization, debouncing, throttling
Requirements
- Follow existing project hook conventions
- Use TypeScript if project uses it
- Include proper cleanup in useEffect
- Add error boundaries where appropriate
- Write tests that cover all hook functionality
- IMPORTANT: Always check existing hooks first to understand project patterns
Notes
- Ask for clarification if the hook requirements are ambiguous
- Suggest optimizations for existing hooks if relevant
- Consider accessibility implications for UI-related hooks
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 · 44 lines · 0 tokens per session scan A dfa97d95b3a4
hooks is a command published in the GitHub repository Justdvp/claude-code-templates (7 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 359 tokens. 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-31.
Other commands, from other repositories
audit-steps
Audit one or all pipelines against layout, frontmatter, topology, and runtime-safety standards — produces a severity-classified report (SEV-0/1/2/3) with cited evidence.
init-deep
Initiates a repository traversal to create localized PIPELINE-CONTEXT.md hierarchical context files.
migrate-pipeline
Migrate an existing pre-v2 per-tier pipeline (.claude/, .opencode/, .agents/codex/) into the unified data-only .superpipelines/ layout — select legacy pipeline, translate frontmatter to canonical agent defs, stage, delta-audit, gate on human approval, then atomically promote, rewrite the registry, and move the legacy…
delete-step
Delete a step from an existing pipeline — select pipeline, select step, perform gap analysis, optionally rewire, audit the delta, then gate on human approval before any deletion.
new-pipeline
Design and scaffold a new named multi-agent pipeline with git preflight, scope selection, pre-gate audit, and entry-skill generation.
new-step
Add a new step to an existing pipeline — select pipeline, choose insertion point, design component, audit the delta, then gate on human approval.