hooks

A helper for creating or improving React hooks, which are reusable functions that add state, data loading, event handling, or other behavior to components.

In plain words
What is it for?
Use it for hooks that fetch data, manage state, handle forms, listen for events, run timers, or consume shared context.
Why use it?
It reduces guesswork around hook structure, project conventions, dependency arrays, error handling, typing, testing, and documentation.

Command for Claude Code

Install

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.

agentmods
npx agentmods add commands/justdvp/claude-code-templates/hooks
Clone the repo
git clone --depth 1 https://github.com/Justdvp/claude-code-templates

Made for: Claude Code.

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 359 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce 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

Measured 2d ago against content hash dfa97d95b3a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

cli-tool/templates/javascript-typescript/examples/react-app/.claude/commands/hooks.md · 44 lines

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:

  1. Examine existing hooks: Check project for existing custom hooks patterns and conventions
  2. Identify hook type: Determine if creating new custom hook, optimizing existing hook, or implementing specific hook pattern
  3. Check TypeScript usage: Verify if project uses TypeScript and follow typing conventions
  4. Implement hook: Create hook with proper:
    • Naming convention (use prefix)
    • TypeScript types and interfaces
    • Proper dependency arrays
    • Error handling
    • Performance optimizations
  5. Add tests: Create comprehensive unit tests using project's testing framework
  6. 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
Changes

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.

  1. 2d ago First seen · 44 lines · 0 tokens per session scan A dfa97d95b3a4

Subscribe to this mod's changes

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.