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 skills/childrentime/reactuse/hook-docsnpx skills add childrentime/reactuse --skill hook-docsgit clone --depth 1 https://github.com/childrentime/reactuseWhat 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.00075 | $0.00873 |
| Opus 5 | $0.00037 | $0.00436 |
| Sonnet 5 | $0.00015 | $0.00175 |
| Haiku 4.5 | $0.00007 | $0.00087 |
Grade A, and why
hook-docs 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
hook-docs — document a hook the ReactUse way
Docs live in the Astro site packages/website-astro. The sidebar and routes are built
automatically from file paths — there is no routes.json or sidebar config to edit.
File locations (one per locale)
packages/website-astro/src/content/docs/{category}/useX.mdx # English
packages/website-astro/src/content/docs-zh-hans/{category}/useX.mdx # 简体中文
packages/website-astro/src/content/docs-zh-hant/{category}/useX.mdx # 繁體中文
{category} is one of: browser, effect, element, state, integrations. The folder
you choose is the category — it sets the registry entry and the canonical URL
(https://reactuse.com/{category}/usex/, lowercase).
Frontmatter
Schema is in packages/website-astro/src/content.config.ts — only title is required;
description, sidebar_label, sidebar_position are optional. Match the existing style:
---
title: useX – State Hook Usage & Examples
sidebar_label: useX
description: "useX is a React hook that … (one sentence, used as the meta description)."
---
Body structure
Follow the established shape (see content/docs/browser/useClipboard.mdx):
# useX
One-line summary of what it does.
A short paragraph explaining the hook, linking to the relevant MDN/spec page where useful.
### When to Use
- bullet of a concrete use case
- another
### Notes
- SSR safety / browser-support caveats
- any gotchas
## Usage
```tsx live
function Demo() {
const [value, set] = useX(0);
return <button onClick={() => set(value + 1)}>{value}</button>;
};
%%API%%
- The ` ```tsx live ` fence renders a live, editable demo. Write the demo **inline** — it is
not imported from the hook's source.
- Keep `%%API%%` as the last line. It's replaced at build time with the generated API table
(from the hook's `interface.ts` JSDoc); if no API doc exists yet it's silently removed.
## Translations
The zh-Hans / zh-Hant files mirror the English structure exactly — translate the prose and
the frontmatter `title`/`description`, keep the code demo identical.
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.
- yesterday First seen · 101 lines · 75 tokens per session scan A e296d74be2fe
hook-docs is a skill published in the GitHub repository childrentime/reactuse (1,047 stars, last pushed 11d ago), licensed Unlicense. It adds 75 tokens to every session and 873 once invoked, about $0.0004 per session on Opus 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-30.
Other skills, from other repositories
react-hooks-composition
Advanced React hooks composition patterns - SWR integration, debounced search, memoized contexts, state machines, and performance optimization.
juniors-best-practice
Juniors-focused React and TypeScript best practices. Use this skill when writing or reviewing code to enforce clear, consistent, and maintainable patterns across common scopes like React, TypeScript, styling, devtools, assets, and Git.
react-hooks-best-practices
React hooks best practices for React application code and custom hook design across DX, optimization, and logic. Use when writing components with hooks, creating or refactoring custom hooks, reviewing hook usage/APIs/internals, checking effects/dependencies/state/refs/callbacks, or improving hook correctness…
reactuse
Practical playbook for React teams to choose and apply reactuse hooks across state, async flows, browser APIs, and UI interactions. Use it when replacing custom hook logic with production-ready patterns that stay compatible with SSR and Next.js.
react-ink
Use this skill when building terminal user interfaces with React Ink - interactive CLI apps, terminal dashboards, progress displays, or keyboard-driven TUI components. Triggers on React Ink, Ink components, terminal UI with React, useInput, useFocus, Box/Text layout, create-ink-app, and any task requiring rich…
vercel-react-best-practices
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance…