react-hook

react-hook is a skill for Claude Code from berkcangumusisik/claude-code-practices. It costs 18 tokens per session (262 once invoked), scanned A, original, MIT.

A generator for custom React hooks written in TypeScript. A React hook is reusable code that lets components share behavior such as loading data, tracking state, or responding to events.

In plain words
What is it for?
Use it to create a hook in the project’s hooks directory, with TypeScript types, tests, cleanup for subscriptions or listeners, and an example of how to call it.
Why use it?
It gives the hook explicit types, handles common asynchronous or cleanup concerns when relevant, and adds a test and usage example. This reduces the work needed to create a hook that fits an existing project.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: positional $N argument.

Good fit Use it to create a hook in the project’s hooks directory, with TypeScript types, tests, cleanup for subscriptions or listeners, and an example of how to call it.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/berkcangumusisik/claude-code-practices/react-hook
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.

Any agent
npx skills add berkcangumusisik/claude-code-practices --skill react-hook
Clone the repo
git clone --depth 1 https://github.com/berkcangumusisik/claude-code-practices

Made for: Claude Code.

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

agentmods badge for react-hook

README.md
[![agentmods](https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/react-hook/github.svg)](https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/react-hook)
Your own site
<a href="https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/react-hook"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/react-hook/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.

agentmods 80×15 button for react-hook

Your own site · 80×15
<a href="https://agentmods.dev/skills/berkcangumusisik/claude-code-practices/react-hook"><img src="https://agentmods.dev/badge/skills/berkcangumusisik/claude-code-practices/react-hook.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 262 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00018 $0.00262
Opus 5.5 $0.00007 $0.00105
Sonnet 5.5 $0.00004 $0.00052
Haiku 4.5 $0.00002 $0.00026

Measured 1mo ago against content hash e897ac8a3daa, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

react-hook 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 1mo 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.

skills/react-hook/SKILL.md · 40 lines

What it actually says

Generate Custom React Hook

Hook name: use$1 (auto-prefix use if not present) Description: $2

  1. Check existing hooks:
ls src/hooks/ 2>/dev/null | head -10

Read 1-2 existing hooks to match style.

  1. Generate the hook:

    • Proper TypeScript generics if applicable
    • Return type explicitly typed
    • Cleanup in useEffect if subscriptions/listeners involved
    • Error and loading states if async
    • Stable callback references with useCallback
    • Memoized values with useMemo where appropriate
  2. Generate a test using @testing-library/react-hooks or renderHook.

  3. Add a usage example comment at the top:

/**
 * @example
 * const { data, isLoading } = useMyHook(id)
 */
  1. Place in src/hooks/use$1.ts (or match project convention).
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. 1mo ago First seen · 40 lines · 18 tokens per session scan A e897ac8a3daa

Subscribe to this mod's changes

react-hook is a skill published in the GitHub repository berkcangumusisik/claude-code-practices (11 stars, last pushed 6mo ago), licensed MIT. It adds 18 tokens to every session and 262 once invoked, about $0.0001 per session on Opus 5.5. 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.

Related

Other skills, from other repositories

react-dev

This skill should be used when building React components with TypeScript, typing hooks, handling events, or when React TypeScript, React 19, Server Components are mentioned. Covers type-safe patterns for React 18-19 including generic components, proper event typing, and routing integration (TanStack Router, React…

chidekina/aria-superpowers · 66 tokens

senior-frontend

Frontend development for React 19, Next.js 15, TypeScript, and Tailwind CSS v4 / Pengembangan frontend dengan React 19, Next.js 15, TypeScript, dan Tailwind CSS v4.

roedyrustam/vibes-plug · 50 tokens

react-frontend

React, TypeScript, and Next.js patterns for frontend development. Use when building React components, managing state, fetching data, optimizing performance, or working with Next.js App Router. Covers React 18-19, hooks, Server Components, and type-safe patterns.

iliaal/whetstone · 57 tokens

typescript-style

Validate TypeScript/React code against style and architectural conventions.

peteski22/agent-pragma · 14 tokens

react-component-design

Designs or reviews React component APIs. Handles prop drilling decisions, composition patterns, controlled/uncontrolled contracts, and minimal public API surfaces for React 18+ TypeScript components. Invoked when creating new components, refactoring existing ones, or reviewing component contracts.

soulcodex/agentic · 56 tokens

senior-frontend

Frontend development skill for React, Next.js, TypeScript, and Tailwind CSS applications. Use when building React components, optimizing Next.js performance, analyzing bundle sizes, scaffolding frontend projects, implementing accessibility, or reviewing frontend code quality.

LuizEduPP/Rememb · 52 tokens