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 agentcathq/webmcp-react --skill webmcp-setupgit clone --depth 1 https://github.com/agentcathq/webmcp-reactWrote 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/agentcathq/webmcp-react/webmcp-setup)<a href="https://agentmods.dev/skills/agentcathq/webmcp-react/webmcp-setup"><img src="https://agentmods.dev/badge/skills/agentcathq/webmcp-react/webmcp-setup/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/agentcathq/webmcp-react/webmcp-setup"><img src="https://agentmods.dev/badge/skills/agentcathq/webmcp-react/webmcp-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 146 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00080 | $0.01196 |
| Opus 5.5 | $0.00032 | $0.00478 |
| Sonnet 5.5 | $0.00016 | $0.00239 |
| Haiku 4.5 | $0.00008 | $0.00120 |
Grade A, and why
webmcp-setup 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Set Up webmcp-react
Overview
webmcp-react exposes React app functionality as typed tools on document.modelContext (the W3C WebMCP API). AI agents discover and call these tools. This skill bootstraps the full setup.
Step 1: Install dependencies
npm install webmcp-react zod
zod is a peer dependency used for typed tool input schemas.
Step 2: Add WebMCPProvider
All useMcpTool calls must be descendants of <WebMCPProvider>. It installs a polyfill when native browser support is absent.
React / Vite
Wrap the app root:
import { WebMCPProvider } from "webmcp-react";
function App() {
return (
<WebMCPProvider name="my-app" version="1.0">
{/* existing app content */}
</WebMCPProvider>
);
}
Next.js (App Router)
Create a client component wrapper since webmcp-react uses browser APIs:
// app/providers.tsx
"use client";
import { WebMCPProvider } from "webmcp-react";
export function Providers({ children }: { children: React.ReactNode }) {
return (
<WebMCPProvider name="my-app" version="1.0">
{children}
</WebMCPProvider>
);
}
Then wrap children in the root layout:
// app/layout.tsx
import { Providers } from "./providers";
export default function RootLayout({ children }: { children: React.ReactNode }) {
return (
<html lang="en">
<body>
<Providers>{children}</Providers>
</body>
</html>
);
}
The library ships with a "use client" banner in its build output, so no transpilePackages config is needed when installing from npm.
Step 3: Create a first tool
Create a simple tool component to verify the wiring works:
// components/mcp-tools.tsx (add "use client" at top if Next.js)
import { useMcpTool } from "webmcp-react";
import { z } from "zod";
export function GreetTool() {
useMcpTool({
name: "greet",
description: "Greet someone by name",
input: z.object({
name: z.string().describe("The name to greet"),
}),
handler: async ({ name }, { signal }) => {
// signal aborts if the agent cancels — forward it to cancellable work
const res = await fetch(`/api/greet?name=${encodeURIComponent(name)}`, { signal });
return { content: [{ type: "text", text: await res.text() }] };
},
});
return null;
}
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 Changed · +2 lines 4bb53b2c3f88
- 1mo ago First seen · 168 lines · 80 tokens per session scan A 665265c3a31b
webmcp-setup is a skill published in the GitHub repository agentcathq/webmcp-react (90 stars, last pushed today), licensed MIT. It adds 80 tokens to every session and 1,196 once invoked, about $0.0003 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-30.
Other skills, from other repositories
react-expert
Expert-level React development with hooks, performance optimization, state management, and modern patterns. Use when the user mentions frontend, hooks, JSX, TypeScript, or Next.js, or when the task involves Modern React, State Management, Forms, or Performance Optimization.
react-hooks-composition
Advanced React hooks composition patterns - SWR integration, debounced search, memoized contexts, state machines, and performance optimization.
fp-react
Practical patterns for using fp-ts with React - hooks, state, forms, data fetching. Works with React 18/19, Next.js 14/15.
zustand-docs
Zustand — small, fast, scalable state management for React. Store creation, hooks, middleware, TypeScript.
react-patterns
A guide to modern React patterns, including components, hooks, server components, actions, forms, state updates, and TypeScript.
Functional Programming in React
Practical patterns for using fp-ts with React - hooks, state, forms, data fetching. Works with React 18/19, Next.js 14/15.