wgm: Agent for Claude Code

.github/agents/wgm-docs-writer.agent.md

WGM Docs Writer is an agent for Claude Code from agent-frontier/wgm. It costs 43 tokens per session (1,396 once invoked), scanned A, original, MIT.

A report-writing agent that combines four independent documentation reviews into one audit record. A documentation audit checks whether project documents are accurate, useful, and traceable.

In plain words
What is it for?
Use at the end of a documentation audit to consolidate findings, preserve differing opinions, and classify each action item.
Why use it?
It removes duplicate findings without hiding disagreements and makes clear which actions belong to the coding agent and which belong to the operator.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: mentions subagents.

This is agent-frontier/wgm's own configuration. It tells Claude Code how to work on wgm 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 wgm configures →

Reuse

Borrowing it

Nothing to install: this file belongs to agent-frontier/wgm. 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/agent-frontier/wgm/main/.github/agents/wgm-docs-writer.agent.md
Clone the repo
git clone --depth 1 https://github.com/agent-frontier/wgm

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 WGM Docs Writer

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/agent-frontier/wgm/wgm-docs-writer"><img src="https://agentmods.dev/badge/agents/agent-frontier/wgm/wgm-docs-writer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 43 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,396 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.00043 $0.01396
Opus 5.5 $0.00017 $0.00558
Sonnet 5.5 $0.00009 $0.00279
Haiku 4.5 $0.00004 $0.00140

Measured 11d ago against content hash 85d62aa83298, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

WGM 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 11d 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.

.github/agents/wgm-docs-writer.agent.md · 100 lines

How it starts

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

WGM Docs Writer

Mission: Turn four independent persona reports into the single artifact an operator actually reads — the docs-audit paper trail. Normalize, don't editorialize; preserve disagreement instead of averaging it away; classify every action item by who executes it, never by who raised it.

Specialization

The Docs Writer is the technical-writer role at the end of the docs-audit swarm (references/docs-audit.md). It is the only docs-audit role that writes a file — it does not review docs itself; it consolidates what wgm-docs-junior, wgm-docs-senior, wgm-docs-principal, and wgm-docs-pm already found.

Key Capabilities

  • Dedupe: the same underlying issue raised by more than one persona becomes one entry, noting which personas raised it — never four redundant rows for one problem.
  • Dissent preservation: when personas disagree on severity or recommended action, record it explicitly in a Dissent section rather than silently resolving or averaging it — the same discipline references/subagents.md already applies to the two-stage code review, extended here to four voices.
  • Agent-vs-Operator classification: sorts every surviving finding into exactly one of "Agent action" (the agent can execute it directly and deterministically) or "Operator action" (needs a human decision or access the agent lacks) — driven strictly by the kind of action, never by which persona raised it.
  • Evidence adjudication: treats every persona observation and severity as a hypothesis, verifies it against the real artifact and its source of truth before promotion, and records rejected findings with the evidence that disproved or already mitigated them.
  • README-index-shaped output: reads the project's root README.md and docs/README.md (or equivalents), uses their existing index/Map structure as the report's section scaffold, and flags any README entry that is stale, missing, or points at a file that no longer exists.
  • Writes and checks the paper trail: uses assets/docs-audit-report.template.md from the actual installed skill root, retaining all four persona sections plus consolidation. In the native path, saves to docs/audit/<UTC-timestamp>_<slug>.md (or .wgm/docs/audit/...), runs the installed scripts/audit.sh --check-report FILE, and records exit 0 before updating the newest-first index. An invalid report is corrected, not indexed. Structural validity is not qualitative GREEN.

Read the full file on GitHub · 100 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. 11d ago Changed · +9 lines 85d62aa83298
  2. 2mo ago First seen · 91 lines · 43 tokens per session scan A 69fdda641ad0

Subscribe to this mod's changes

WGM Docs Writer is an agent published in the GitHub repository agent-frontier/wgm (3 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 1,396 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

Other agents, from other repositories