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/webmcp-org/npm-packages/docs-authoringnpx skills add WebMCP-org/npm-packages --skill docs-authoringgit clone --depth 1 https://github.com/WebMCP-org/npm-packagesWrote 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/webmcp-org/npm-packages/docs-authoring)<a href="https://agentmods.dev/skills/webmcp-org/npm-packages/docs-authoring"><img src="https://agentmods.dev/badge/skills/webmcp-org/npm-packages/docs-authoring.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.00056 | $0.04770 |
| Opus 5 | $0.00028 | $0.02385 |
| Sonnet 5 | $0.00011 | $0.00954 |
| Haiku 4.5 | $0.00006 | $0.00477 |
Grade A, and why
docs-authoring 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 5d 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WebMCP Documentation: Authoring Guide
Reference for writing and editing the WebMCP docs. The repo-wide agent instructions live in the root AGENTS.md; this file covers the docs-specific rules (Diataxis, writing style, Mintlify components, source-of-truth boundaries).
What this is
Documentation for WebMCP, a Community Group proposal for exposing website tools through document.modelContext. Built with
Mintlify. Live at
docs.mcp-b.ai.
Site structure
apps/documentation-website/docs.json is the single source of truth for navigation,
pages, groups, and hierarchy. Read it first.
| Tab | Path prefix | Diataxis type |
|---|---|---|
| Home | index, start-here/ |
Landing + routing |
| Packages | packages/, reference/webmcp/ |
Information-oriented |
| Tutorials | tutorials/ |
Learning-oriented |
| How-To Guides | how-to/ |
Goal-oriented |
| Explanation | explanation/ |
Understanding-oriented |
Every package gets an overview page and a reference page under
packages/<name>/. The reference/webmcp/ pages route proposal and platform
details to upstream sources and sit in the same tab.
explanation/design/spec-status-and-limitations keeps its legacy URL but is a
reference directory in the WebMCP platforms and agents navigation group.
Key files
| File | Purpose |
|---|---|
apps/documentation-website/docs.json |
Navigation, theme, config. Do not modify without explicit request. |
../diataxis/SKILL.md |
Diataxis framework overview and compass |
../diataxis/references/ |
17 unabridged Diataxis reference pages from diataxis.fr |
../mintlify/SKILL.md |
Mintlify best practices (components, navigation, frontmatter, deployment) |
references/design-system.mdx |
Brand colors, typography, Mintlify component examples |
What ships with it
1 file 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.
- 5d ago First seen · 346 lines · 56 tokens per session scan A c224f5f29527
docs-authoring is a skill published in the GitHub repository WebMCP-org/npm-packages (91 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 4,770 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…