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 skills add niels-emmer/myace --skill doc-standardsgit clone --depth 1 https://github.com/niels-emmer/myaceWrote 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/niels-emmer/myace/doc-standards)<a href="https://agentmods.dev/skills/niels-emmer/myace/doc-standards"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/doc-standards/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.
<a href="https://agentmods.dev/skills/niels-emmer/myace/doc-standards"><img src="https://agentmods.dev/badge/skills/niels-emmer/myace/doc-standards.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00022 | $0.00668 |
| Opus 5.5 | $0.00009 | $0.00267 |
| Sonnet 5.5 | $0.00004 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
Documentation Standards 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 1mo 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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Give any doc you write or edit a consistent shape so readers (and agents) can scan it, trust it, and find what they need without re-deriving your conventions each time. Use this whenever you're writing a README section, a docs/ page, an agent-facing instruction file (AGENTS.md/CLAUDE.md-style), or reviewing someone else's doc for structural issues.
When to use it
- Writing a new doc section or page from scratch.
- Reviewing an existing doc for structure, not just factual accuracy (pair with the drift-check skill for accuracy).
- Deciding whether new content belongs in an existing doc or needs its own page.
Conventions
Structure
- Lead with what the thing is and why it exists before diving into how to use it. A reader deciding whether to keep reading needs that in the first sentence or two.
- Use headings that describe content, not narrate process ("Configuration" not "How We Set This Up"). Keep heading depth shallow — two or three levels is almost always enough.
- Put the most commonly needed information first (quickstart, common commands) and push edge cases, advanced options, and rationale further down or into a linked doc.
Examples
- Every non-trivial command or API shown should be a working, copy-pasteable example, not pseudocode. If you can't verify it runs, say so explicitly rather than presenting it as tested.
- Show the expected output or result when it's not obvious, especially for CLI commands and API calls — readers verify they did it right by comparing output, not by re-reading the instructions.
Language
- Avoid unexplained jargon and internal shorthand. If a term is project-specific (a service name, an internal abbreviation), define it on first use or link to where it's defined.
- Avoid references that assume shared context the reader doesn't have — no "as discussed," "the fix from before," or ticket/PR numbers without enough surrounding explanation to be useful standalone.
- Prefer active voice and direct imperatives for instructions ("Run X," not "X should be run").
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.
- 1mo ago First seen · 43 lines · 22 tokens per session scan A 8a084b7278d2
Documentation Standards is a skill published in the GitHub repository niels-emmer/myace (1 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 668 once invoked, about $0.0001 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.
Other skills, from other repositories
eclipse-license-check
Vet third-party dependencies for an Eclipse Foundation project with the Eclipse Dash License Tool — license checks, "do I need to vet X?" questions, IPLab review filing, and release IP due diligence. Use whenever the user mentions Eclipse license checking, dash-licenses, the Dash License Tool, IPLab, third-party…
idiomatic-go
Apply Go community idioms for API and package design, error and concurrency patterns, naming (initialisms, stutter, receivers), generics vs interfaces, and Go code review — including PR or diff review, questions about "the Go way", pointer vs value receivers, channels vs mutexes, and building Go language tooling…
go-documentation
Write idiomatic Go doc comments that render correctly on pkg.go.dev — package comments, doc.go, exported-symbol comments, testable Example functions, deprecation notices — and publish or debug modules on pkg.go.dev (pkgsite, the module proxy). Use when writing or reviewing Go documentation, or when a developer used to…
publish-vscode-extension
Publish a VS Code extension to the VS Code Marketplace and/or Open VSX Registry. Use when the user wants to publish, ship, or release a VS Code extension; audit or improve manifest, listing, or release setup; build or upload a .vsix; set up vsce or ovsx; create a marketplace publisher or Open VSX namespace; configure…
domainmodel-dsl
Read, write, and modify Domain Model DSL files (.dmodel) — datatypes, entities with inheritance and multi-valued features, and nested packages with qualified cross-references. Use when the user wants to create, edit, explain, or debug a domain model in this DSL, including resolving references across packages.
statemachine-dsl
Read, write, and modify Statemachine DSL files (.statemachine). Use when the user wants to create, edit, explain, or debug a state machine written in this textual DSL — defining states, events, commands, and transitions, or generating a machine from a description.