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/state-management)<a href="https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/state-management"><img src="https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/state-management/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/commands/swesmith/davila7__claude-code-templates.734b8a50/state-management"><img src="https://agentmods.dev/badge/commands/swesmith/davila7__claude-code-templates.734b8a50/state-management.svg" alt="Reviewed on agentmods" width="80" 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.00371 |
| Opus 5 | $0.00000 | $0.00186 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
state-management 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 5d 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 state-management — 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 State Management
Implement state management solution for $ARGUMENTS following project conventions.
Task
Set up or optimize state management based on the requirements:
- Analyze current setup: Check existing state management approach and project structure
- Determine solution: Based on requirements, choose appropriate state management:
- Context API for simple, localized state
- Redux Toolkit for complex, global state
- Zustand for lightweight global state
- Custom hooks for component-level state
- Examine dependencies: Check package.json for existing state management libraries
- Implement solution: Create store, providers, and hooks with proper TypeScript types
- Set up middleware: Add devtools, persistence, or other middleware as needed
- Create typed hooks: Generate properly typed selectors and dispatch hooks
- Add tests: Write unit tests for state logic and reducers
- Update providers: Integrate with app's provider hierarchy
Implementation Requirements
- Follow project's TypeScript conventions
- Use existing state management patterns if present
- Create proper type definitions for state shape
- Include error handling and loading states
- Add proper debugging setup (devtools)
- Consider performance optimizations (selectors, memoization)
State Management Selection Guide
Choose based on complexity:
- Simple state: React hooks + Context API
- Medium complexity: Zustand or custom hooks
- Complex state: Redux Toolkit with RTK Query
- Form state: React Hook Form or Formik
Important Notes
- ALWAYS check existing state management first
- Don't install new dependencies without asking
- Follow project's folder structure for state files
- Consider server state vs client state separation
- Add proper TypeScript types for all state interfaces
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.
- 5d ago First seen · 45 lines · 0 tokens per session scan A 473be148b662
state-management 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 371 tokens. A static security scan graded it A with 0 findings. It is 100% identical to state-management, 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).