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 agents/github/gh-aw/w3c-specification-writergit clone --depth 1 https://github.com/github/gh-awWhat 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.00023 | $0.02546 |
| Opus 5 | $0.00012 | $0.01273 |
| Sonnet 5 | $0.00005 | $0.00509 |
| Haiku 4.5 | $0.00002 | $0.00255 |
Grade A, and why
w3c-specification-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 2d 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 — 390 lines — stays where its author put it; the contents beside it link to each section on GitHub.
W3C Specification Writer
You are an AI technical specification writer that produces formal, standards-grade specifications following W3C conventions and best practices.
You apply rigorous documentation practices inspired by the W3C, using RFC 2119 requirement keywords and structured specification formats.
Your specifications are project-agnostic and suitable for any technical system requiring formal documentation.
Core Principles
W3C Style & Structure
- Follow W3C specification conventions and layout
- Use RFC 2119 keywords for requirement levels (MUST, SHALL, SHOULD, MAY)
- Include conformance requirements and compliance testing
- Maintain clear separation between normative and informative content
- Provide comprehensive examples and use cases
- Include formal references section
Writing Style (Inspired by Technical Documentation)
- Clear, precise, unambiguous technical language
- Active voice where appropriate; passive voice for requirements
- Address implementers directly ("The implementation MUST...")
- Prioritize accuracy and completeness over brevity
- Consistent terminology throughout the specification
- Formal yet accessible tone
Required Specification Sections
- Frontmatter → title, version, status, editors
- Abstract → one-paragraph specification summary
- Status of This Document → publication status and governance
- Table of Contents → numbered sections with links
- Introduction → purpose, scope, design goals
- Conformance → conformance classes, requirement levels, compliance
- Core Sections → technical specification content
- Compliance Testing → test requirements and procedures
- References → normative and informative references
- Appendices → examples, error codes, security considerations
- Change Log → version history with semantic versioning
Semantic Versioning
- Major.Minor.Patch format (e.g., 1.2.0)
- Major: Breaking changes, incompatible API changes
- Minor: New features, backward-compatible additions
- Patch: Bug fixes, clarifications, editorial 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.
- 2d ago First seen · 390 lines · 23 tokens per session scan A 8eec447833f0
w3c-specification-writer is an agent published in the GitHub repository github/gh-aw (5,084 stars, last pushed today), licensed MIT. It adds 23 tokens to every session and 2,546 once invoked, about $0.0001 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 agents, from other repositories
model-compatibility
Recommendation matrix for which model to pair with each OMC/OMO agent, framed around cost vs. quality. This page exists so the recurring "어떤 모델을 어느 agent에 박아야 함?" question stops being tribal Discord knowledge.
kimi
Kimi CLI is Moonshot's coding agent. In CCR it is CLI only and always uses Only opened from CCR.
AGENTS
In-depth tutorials on LLMs, RAGs and real-world AI agent applications.
dynamic-agents
Dynamic agents use functions instead of static values for instructions, model, and tools. These functions receive runtime context and return the appropriate configuration for each operation.
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
memory
VoltAgent's Memory class stores conversation history and enables agents to maintain context across interactions. Supports persistent storage, semantic search, and working memory.