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 hams-ollo/zen-agent-skills --skill doc-authorgit clone --depth 1 https://github.com/hams-ollo/zen-agent-skillsWrote 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/hams-ollo/zen-agent-skills/doc-author)<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/doc-author"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/doc-author/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/hams-ollo/zen-agent-skills/doc-author"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/doc-author.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.00122 | $0.01231 |
| Opus 5.5 | $0.00049 | $0.00492 |
| Sonnet 5.5 | $0.00024 | $0.00246 |
| Haiku 4.5 | $0.00012 | $0.00123 |
Grade A, and why
doc-author 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 7d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc author
Create documentation that is accurate, well-structured, and matched to its reader. The two ways documentation fails are being wrong (it describes code that does not exist or has drifted) and being shapeless (a wall of text with no reader in mind). This skill guards against both: ground every claim in the real repository, and pick a structure that fits the document type and audience. When the document already exists and needs updating rather than creating, use doc-revise instead. When the user does not yet know which document is wrong, use doc-sync to find out first.
Ground it in the code first
Never document from assumption. Before writing, read the parts of the repository the document will describe: the relevant source, the AGENTS.md or CLAUDE.md, the config, the entry points. If you state that a command runs the tests or that a module does X, it should be because you saw it, not because it is a reasonable guess. Drifted docs are worse than missing ones because readers trust them.
Identify the document type and reader
Ask, or infer from the request, two things: what kind of document this is, and who reads it. The structure follows from those. Common types and their spines:
- README (technical): what the project is, quick start, install and run, key commands, layout, where to go next. Lead with the one-sentence description and the fastest path to running it.
- README (non-technical): what this does and why it matters, in plain language, no jargon, with the mental model built from the ground up. The user asks for this often; assume the reader has no domain knowledge and explain the concepts, not just the steps.
- Architecture doc: the system in Mermaid diagrams (component, flow, sequence, state as fits), the major pieces and how they connect, the key decisions and why. Diagrams are Mermaid fenced blocks, never ASCII.
- Setup or deployment guide: prerequisites, step-by-step, configuration, verification, and common failure modes. Every step should be something the reader can actually execute and check.
- Contributing guide: how to get set up, conventions, the change and review workflow, how to run the checks.
- Design doc or ADR: the problem, the options considered, the decision, the rationale, and the consequences. Name the tradeoffs honestly.
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.
- 7d ago Changed · -5 lines · -77 tokens per session 62b51c784b95
- 1mo ago Changed · +7 lines f5555cf59c0c
- 2mo ago First seen · 56 lines · 199 tokens per session scan A 952a122c4508
doc-author is a skill published in the GitHub repository hams-ollo/zen-agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 122 tokens to every session and 1,231 once invoked, about $0.0005 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
review
Use when explicitly invoked to review a branch diff (or any diff or files pointed at) with a find-only subagent covering rubric and conventions, change conformance against the AC-N and their runtime-verification evidence, and documentation consistency — one plain-text verdict that reaches lgtm only when no dimension…
implement
Use when explicitly invoked to execute a change's tasks.md from the first unticked step: implement each task, run its validation, commit, then run the quality gate and verify every acceptance criterion by observed behavior. Needs no conversation context — the change folder is the whole input. Trigger on…
archive
Use when explicitly invoked to close out a change whose branch has already merged: confirm the merge from git alone, then move the change folder under changes/archive/ with its ship date. Trigger on '/sw:archive', '$sw:archive', 'archive this change', or a request to close out a merged change.
ship
Use when explicitly invoked to run the whole change ladder without stopping — ticket, plan, implementation, quality gate, runtime verification, review to lgtm — deciding every open question autonomously and recording each decision in proposal.md. Trigger on '/sw:ship', '$sw:ship', or a request to take something from…
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…