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/webmaxru/is-ai-native/webmcpnpx skills add webmaxru/is-ai-native --skill webmcpgit clone --depth 1 https://github.com/webmaxru/is-ai-nativeWrote 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/webmaxru/is-ai-native/webmcp)<a href="https://agentmods.dev/skills/webmaxru/is-ai-native/webmcp"><img src="https://agentmods.dev/badge/skills/webmaxru/is-ai-native/webmcp.svg" alt="Measured on agentmods" 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 | $0.00087 | $0.01603 |
| Opus 5 | $0.00044 | $0.00801 |
| Sonnet 5 | $0.00017 | $0.00321 |
| Haiku 4.5 | $0.00009 | $0.00160 |
Grade A, and why
webmcp 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WebMCP
Procedures
Step 1: Identify the browser integration surface
- Inspect the workspace for browser entry points, UI handlers, and any existing app state or form handling layer.
- Execute
node scripts/find-webmcp-targets.mjs .to inventory likely frontend files and existing WebMCP markers when a Node runtime is available. - If a Node runtime is unavailable, inspect the nearest
package.json, HTML entry point, and framework bootstrap files manually to identify the browser app boundary. - If the workspace contains multiple frontend apps, prefer the app that contains the active route, component, or user-requested feature surface.
- If the inventory still leaves multiple plausible frontend targets, stop and ask the user which app should receive the WebMCP integration.
- If the project is not a browser web app, stop and explain that this skill does not apply.
Step 2: Choose the WebMCP shape
- Read
references/webmcp-reference.mdbefore writing code. - Read
references/declarative-api.mdwhen the feature can be expressed as an HTML form flow or needs agent-invoked submit handling. - Read
references/compatibility.mdwhen native availability, Chrome preview setup, or draft-versus-preview behavior matters. - Read
references/troubleshooting.mdwhen registration, schema serialization, or agent-driven form execution fails. - Verify that the integration runs in a secure window browsing context.
- If the feature must run on the server, in a worker, or headlessly without a visible browsing context, stop and explain the platform limitation.
- Choose the imperative API when the tool wraps existing JavaScript logic, requires dynamic registration, or needs
ModelContextClient.requestUserInteraction(). - Choose the declarative API when the user flow already maps cleanly to a form submission and the page can keep the human-visible form in sync with agent activity.
- Keep tool names, descriptions, and parameters explicit and positive, and prefer atomic tools over overlapping variants.
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 71 lines · 87 tokens per session scan A c966dd40a881
webmcp is a skill published in the GitHub repository webmaxru/is-ai-native (5 stars, last pushed 12d ago), licensed MIT. It adds 87 tokens to every session and 1,603 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-31.
Other skills, from other repositories
pr-screenshots
Capture Playwright screenshots and embed them in GitHub PR descriptions.
web-games
Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
webapp-testing
Web application testing principles. E2E, Playwright, deep audit strategies.
pr-lifecycle
Complete issue → PR → merge lifecycle with readiness checks.
cross-squad-communication
Protocol for sending queries, delegating tasks, and sharing context between independent Squad instances across different repositories.
distributed-mesh
How to coordinate with squads on different machines using git as transport.