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 skills add Sannnao/react-docs-mcp --skill using-react-hook-form-docs-mcpgit clone --depth 1 https://github.com/Sannnao/react-docs-mcpWrote 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/skills/sannnao/react-docs-mcp/using-react-hook-form-docs-mcp)<a href="https://agentmods.dev/skills/sannnao/react-docs-mcp/using-react-hook-form-docs-mcp"><img src="https://agentmods.dev/badge/skills/sannnao/react-docs-mcp/using-react-hook-form-docs-mcp/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/skills/sannnao/react-docs-mcp/using-react-hook-form-docs-mcp"><img src="https://agentmods.dev/badge/skills/sannnao/react-docs-mcp/using-react-hook-form-docs-mcp.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.00041 | $0.00343 |
| Opus 5.5 | $0.00016 | $0.00137 |
| Sonnet 5.5 | $0.00008 | $0.00069 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
using-react-hook-form-docs-mcp 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- using-react-hook-form-docs-mcp — 100% identical, 0 lines differ
What it actually says
Using react-hook-form-docs-mcp
When this MCP server is connected, prefer it over recalling React Hook Form APIs from memory — training data goes stale, this tool indexes the live official docs.
Workflow
- Search first. Call
search_react_hook_form_docswith a natural-language query before writing form code that touches an API you're not 100% certain about (register options, validation rules, useFieldArray methods, resolver behavior). Results include a relevance-ranked snippet and aurl. - Drill in only when needed. If the search snippet isn't enough, call
get_docwith thepathfrom a search result. It returns a ~1500 char summary plus a structure outline by default. - Use
full: truesparingly. Passfull: truetoget_doconly for long guides — Advanced Usage, the v7→v8 migration guide — where truncation would hide later steps. Don't default tofullfor short API reference pages. - Search unfiltered by default. Only
docs/(the API reference) is a real section; guide pages (get-started, advanced-usage, faqs, ts) live at the content root and are missed by any section filter. - Refresh if docs seem stale. Call
update_docsto pull the latest commit before concluding an API doesn't exist.
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.
- 1mo ago First seen · 17 lines · 41 tokens per session scan A e7702bdb6fbb
using-react-hook-form-docs-mcp is a skill published in the GitHub repository Sannnao/react-docs-mcp (8 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 343 once invoked, about $0.0002 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.
Other skills, from other repositories
tamagui-upgrade-v3
Migrate an app from Tamagui v2 (or v1) to v3. Use when upgrading Tamagui versions, removing $ token prefixes, converting hoverStyle/pressStyle/media/theme/platform condition objects to flat values, running the flat-values codemod, or fixing v3 breaking changes. Triggers: "upgrade tamagui", "migrate to v3", "flat…
tamagui
Universal React UI framework for web and native with flat conditional values. Use when building cross-platform apps with Tamagui, writing styled components, or applying tokens, themes, animations, and media queries.
tamagui-v6-config
Tamagui v6 theme system: the light/dark/accent/brand/inverse/level/active theme family, the background-active one-off key, and recipe-tree authoring with createV6Config. Use when choosing a theme for a surface, building a selected/emphasis state, or authoring a custom v6 colors pack.
tamagui-theme-generator
Generate custom Tamagui themes, color palettes, and preview URLs. Use when creating or refining a color scheme, authoring light/dark palettes with brand accents, or previewing generated themes in the browser.
git-safety
Git safety rules. INVOKE WHEN: git push, force push, git reset, git clean, destructive git, push force, reset hard. NEVER force push or do destructive git operations.
release-safety
Release safety rules. INVOKE WHEN: yarn release, npm publish, release canary, release packages, publishing, skip checks, skip tests. NEVER skip checks or tests without explicit permission.