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-revisegit 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-revise)<a href="https://agentmods.dev/skills/hams-ollo/zen-agent-skills/doc-revise"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/doc-revise/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-revise"><img src="https://agentmods.dev/badge/skills/hams-ollo/zen-agent-skills/doc-revise.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.00128 | $0.01011 |
| Opus 5.5 | $0.00051 | $0.00404 |
| Sonnet 5.5 | $0.00026 | $0.00202 |
| Haiku 4.5 | $0.00013 | $0.00101 |
Grade A, and why
doc-revise 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 — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Doc revise
Change existing documentation surgically. The reader already relies on these docs, so the goal is the smallest change that satisfies the request while keeping the document's voice, structure, and correctness intact. The two failure modes are doing too little (leaving the doc internally inconsistent or its links broken) and doing too much (rewriting whole sections that were fine, flattening the author's voice). Aim between them. When the document does not exist yet and needs creating from scratch, use doc-author instead. When the user does not yet know which document drifted, use doc-sync to find out first; it composes this skill's editing discipline when it applies an approved correction.
Read before you edit
Read the target document in full, and read the neighbors it links to or that link to it, before changing anything. You cannot keep a set of docs consistent if you have only seen one. If the revision is about reflecting code or state changes, read the actual current code or state too, so the update is grounded and not a guess.
Common revision shapes
Most requests are one of these. Recognize which, because each has a different risk.
- Reconcile with reality: the code or project moved and the doc is stale. Find the specific claims that drifted and correct just those. Do not rewrite passages that are still accurate.
- Fix links and references after a move: the user reorganized files or folders and references are now broken. This is common and mechanical: find every internal link and path reference across the affected docs, resolve each against the new locations, and update the broken ones. Verify, do not assume, that each target now exists at the path you wrote.
- Keep a doc set consistent: a change in one document implies changes in others (a renamed concept, a moved section, a new component). Propagate the change across all affected docs so they agree.
- Move items between docs: for example, completed items from a TODO into a CHANGELOG with a dated line, or an item from a roadmap into a task file. Preserve the entry's meaning, match the destination's format, and remove it cleanly from the source.
- Targeted addition or formatting: add a subsection, insert new content the user provides, add section emojis, adjust structure. Touch only what the request names.
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 · -4 lines · -68 tokens per session 926bc780c273
- 1mo ago Changed · +7 lines 9082da59eef0
- 2mo ago First seen · 47 lines · 196 tokens per session scan A a4efc677d6b2
doc-revise is a skill published in the GitHub repository hams-ollo/zen-agent-skills (2 stars, last pushed 7d ago), licensed MIT. It adds 128 tokens to every session and 1,011 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"…