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.
git clone --depth 1 https://github.com/swesmith/davila7__claude-code-templates.734b8a50Wrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/hooks)<a href="https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/hooks"><img src="https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/hooks.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $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 3d 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.
This is a copy
100% identical to hooks — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 3d ago First seen · 44 lines · 0 tokens per session scan A dfa97d95b3a4
hooks is a command published in the GitHub repository swesmith/davila7__claude-code-templates.734b8a50 (2 stars, last pushed 8mo 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. It is 100% identical to hooks, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
ui-component-create
Create a UI Component in /components/ui with variants, tests, and preview.
add-tests
Add comprehensive tests for React components or functions using React Testing Library and Jest.
component-scaffold
You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, styles, and documentation following modern best practices.
create-component
Create a frontend component with proper structure, types, and accessibility.
component-scaffold
You are a React component architecture expert specializing in scaffolding production-ready, accessible, and performant components. Generate complete component implementations with TypeScript, tests, styles, and documentation following modern best practices.
dark-factory-validate
Run Dark Factory validation — Python backend (ruff + mypy + pytest) + React frontend (tsc + biome + vitest).