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/sannnao/react-docs-mcp/using-react-hook-form-docs-mcpnpx skills add Sannnao/react-docs-mcp --skill using-react-hook-form-docs-mcpgit clone --depth 1 https://github.com/Sannnao/react-docs-mcpWhat 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.00041 | $0.00343 |
| Opus 5 | $0.00020 | $0.00171 |
| Sonnet 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 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.
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.
- 3d 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 1mo ago), licensed MIT. It adds 41 tokens to every session and 343 once invoked, about $0.0002 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-31.
Other skills, from other repositories
using-react-hook-form-docs-mcp
How to effectively use the react-hook-form-docs-mcp search and doc-retrieval tools instead of relying on training-data memory of React Hook Form APIs.
using-react-native-docs-mcp
How to effectively use the react-native-docs-mcp search and doc-retrieval tools instead of relying on training-data memory of React Native APIs.
tamagui
Universal React UI framework for web and native. Use when building cross-platform apps with Tamagui, creating styled components with styled(), configuring design tokens/themes, using Tamagui UI components, or working with animations. Triggers: "tamagui", "styled()", "$token", "XStack/YStack", "useTheme", "@tamagui/"…
truesheet-usage
Consumer-side guide for integrating @lodev09/react-native-true-sheet into a React Native app. Use this skill whenever the user wants to add, configure, control, or debug a bottom sheet using TrueSheet — including ref-based sheets, named global sheets, web support with TrueSheetProvider/useTrueSheet, React Navigation…
writing-react-native-storybook-stories
Create and edit React Native Storybook stories using Component Story Format (CSF). Use when writing .stories.tsx files, adding stories to React Native components, configuring Storybook addons (controls, actions, backgrounds, notes), setting up argTypes, decorators, parameters, or working with portable stories for…
setup-react-native-storybook
Set up Storybook for React Native in Expo, React Native CLI, or Re.Pack projects. Use when adding Storybook to a project, configuring metro.config.js with withStorybook, creating .rnstorybook configuration files, setting up Storybook routes in Expo Router, configuring getStorybookUI, or adding the StorybookPlugin to a…