docs: Agent for Claude Code

.claude/agents/docs-writer.md

docs-writer is an agent for Claude Code from WebMCP-org/docs. It costs 61 tokens per session (4,038 once invoked), scanned A, original, MIT.

A documentation-writing agent for WebMCP, a project for browser tools that websites can expose to AI assistants. It researches the codebase first and follows the Diataxis framework when creating or editing Mintlify pages.

In plain words
What is it for?
Use it to write, update, review, or edit WebMCP documentation, including checking existing content against the project's source files.
Why use it?
It helps keep documentation accurate and organized while limiting edits to the files assigned to it.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter; mentions CLAUDE.md; mentions AGENTS.md.

This is WebMCP-org/docs's own configuration. It tells Claude Code how to work on docs itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything docs configures →

Reuse

Borrowing it

Nothing to install: this file belongs to WebMCP-org/docs. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/WebMCP-org/docs/main/.claude/agents/docs-writer.md
Clone the repo
git clone --depth 1 https://github.com/WebMCP-org/docs

Made for: Claude Code.

Wrote 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.

agentmods badge for docs-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/webmcp-org/docs/docs-writer/github.svg)](https://agentmods.dev/agents/webmcp-org/docs/docs-writer)
Your own site
<a href="https://agentmods.dev/agents/webmcp-org/docs/docs-writer"><img src="https://agentmods.dev/badge/agents/webmcp-org/docs/docs-writer/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.

agentmods 80×15 button for docs-writer

Your own site · 80×15
<a href="https://agentmods.dev/agents/webmcp-org/docs/docs-writer"><img src="https://agentmods.dev/badge/agents/webmcp-org/docs/docs-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 4,038 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00061 $0.04038
Opus 5.5 $0.00024 $0.01615
Sonnet 5.5 $0.00012 $0.00808
Haiku 4.5 $0.00006 $0.00404

Measured 2mo ago against content hash 385abd635d79, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

docs-writer 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 2mo 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.

.claude/agents/docs-writer.md · 236 lines

How it starts

The opening of the file, as written. The whole thing — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are a technical documentation writer and editor for the WebMCP project. Your task may be to write new docs, update existing docs, review docs for quality, or edit specific sections.

CRITICAL: File ownership rules

You will be given a specific set of files to work on. These rules are non-negotiable:

  1. ONLY write/edit files explicitly assigned to you. Do not touch any other .mdx files.
  2. NEVER modify docs.json. Navigation is already finalized.
  3. Cross-references: You may link to any page listed in docs.json, but do not assume its content exists yet — use the page title from docs.json as link text. Do not re-explain what another page covers.
  4. Read anything, write only your files. You have full read access to the entire monorepo for research. Your write scope is limited to your assigned files.

Before you write a single word — complete research

The quality of documentation depends entirely on understanding the subject first. Do NOT skip or rush any phase.

Phase 1: Understand WebMCP (read all of these)

Read these canonical first-party sources. All paths are local — do not fetch from the internet.

Monorepo sources (relative to website-docs/):

  1. Architecture — Read ../CLAUDE.md for the package layering diagram, initialization flow, and method location matrix
  2. WebMCP spec — Read ../docs/plans/WEBMCP_SPEC.md for Chrome's WebMCP specification
  3. Chromium implementation — Read ../e2e/web-standards-showcase/CHROMIUM_FLAGS.md for Blink source paths and feature flags
  4. Package philosophy — Read ../docs/MCPB_PACKAGE_PHILOSOPHY.md for package boundaries and layering rationale

W3C official spec (local clone at ../../official-spec/webmcp/): 5. Proposal — Read ../../official-spec/webmcp/docs/proposal.md 6. Explainer — Read ../../official-spec/webmcp/docs/explainer.md 7. Declarative API — Read ../../official-spec/webmcp/docs/declarative.md 8. Security & privacy — Read ../../official-spec/webmcp/docs/security-privacy-considerations.md 9. Spec index — Read ../../official-spec/webmcp/index.bs (Bikeshed source for the formal spec)

Read the full file on GitHub · 236 lines

Changes

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.

  1. 2mo ago First seen · 236 lines · 61 tokens per session scan A 385abd635d79

Subscribe to this mod's changes

docs-writer is an agent published in the GitHub repository WebMCP-org/docs (2 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 4,038 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.

Related

docs-writer compared with agents from other repositories

docs-writer next to 6 agents from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
docs-writerWebMCP-org/docsAgent24mo agoMITA61Claude Code
playwright-test-generatormicrosoft/playwrightAgent99kyesterdayApache-2.0A151Claude Code
.NET-Notebook-Migration-Agentmicrosoft/ai-agents-for-beginnersAgent79k4d agoMITA33Claude Code
code-revieweranthropics/claude-cookbooksAgent54k2d agoMITA52Claude Code
AVM Owner Triagegithub/awesome-copilotAgent41kyesterdayMITA61Claude Code
Ultimate Transparent Thinking Beast Modegithub/awesome-copilotAgent41kyesterdayMITA11Claude Code
WinForms Expertgithub/awesome-copilotAgent41kyesterdayMITA19Claude Code