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 afaraha8403/balakit --skill documentation-writergit clone --depth 1 https://github.com/afaraha8403/balakitWrote 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/afaraha8403/balakit/documentation-writer)<a href="https://agentmods.dev/skills/afaraha8403/balakit/documentation-writer"><img src="https://agentmods.dev/badge/skills/afaraha8403/balakit/documentation-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.
<a href="https://agentmods.dev/skills/afaraha8403/balakit/documentation-writer"><img src="https://agentmods.dev/badge/skills/afaraha8403/balakit/documentation-writer.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.00099 | $0.00950 |
| Opus 5.5 | $0.00040 | $0.00380 |
| Sonnet 5.5 | $0.00020 | $0.00190 |
| Haiku 4.5 | $0.00010 | $0.00095 |
Grade A, and why
documentation-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 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Writer
Leading words: research-first, Diátaxis mode, BLUF, STE, Global English, evidence-aware, phase separation.
Research-first technical documentation. Chat stays Caveman; the document is Standard Professional Mode.
Copy these phases into the todo list verbatim. A skipped phase stays with
skip: <reason>.
- Discover — list every file/API/feature the docs must cover.
- Research — primary sources for versions, flags, install commands.
- Outline — name the Diátaxis mode; BLUF per section.
- Draft — STE / Global English; slop catalog for artifacts.
- Verify — examples run; citations still match.
Mode table: references/diataxis.md. Sentence craft: references/style.md. Slop ids: references/slop-catalog.md.
Subagents
If the host can launch a Task / explore subagent, use a read-only explore
pass for a large or unfamiliar codebase before drafting. Use web search for
anything version-sensitive. Do not assume those tools exist.
Phase 1 — Discover
Read relevant files. Delegate broad mapping to explore when available.
Exit: you can list every file/API/feature the docs must cover.
🛑 Do not proceed to Research until the user confirms the scope (or you are
explicitly operating solo and the scope is unambiguous). Ask with the host's
structured question tool. Prompt in plain English. Last option:
Say this in plain English (meta: rephrase + example, do not advance).
Phase 2 — Research
Web research before asserting facts about APIs, CLI flags, install commands, LTS timelines, or security claims. Prefer primary sources. Capture citations. If sources conflict, say what is uncertain.
Exit: every claim you will make has a source link. 🛑 Do not proceed to Outline until Research is complete.
Phase 3 — Outline
Name the Diátaxis mode. Headings, audience, prerequisites. BLUF: lead each section with the direct answer in 40–60 words.
Exit: skeleton approved.
🛑 Present the outline. Do not draft until confirmed. Ask with the host's
structured question tool. Prompt in plain English. Last option:
Say this in plain English (meta: rephrase + example, do not advance).
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed · +4 lines 6b8cffb9d878
- 1mo ago Changed · -50 lines · +4 tokens per session 47a697da2b4e
- 1mo ago First seen · 153 lines · 95 tokens per session scan A d20a201d20b0
documentation-writer is a skill published in the GitHub repository afaraha8403/balakit (1 stars, last pushed 1mo ago), licensed MIT. It adds 99 tokens to every session and 950 once invoked, about $0.0004 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
diataxis-docs-framework
Enterprise technical documentation best practices, patterns, and frameworks for developer and partner adoption. Covers content architecture (Diataxis four quadrants), 14 content types (tutorials, how-to guides, API reference, SDK docs, migration guides, changelogs, runbooks, integration guides, troubleshooting…
documentation-standards
Use when writing README files, API documentation, user guides, or technical documentation following industry standards from Google, Microsoft, and GitLab style guides.
diataxis
Classify, create, review, and maintain documentation using the Diátaxis framework — the four-quadrant system (tutorials, how-to guides, reference, explanation) that separates documentation by user need. Use this skill whenever the user wants to classify documentation into quadrants, perform a documentation gap…
api-documentation
Patterns and templates for creating comprehensive API documentation using OpenAPI/Swagger, AsyncAPI, and manual documentation approaches. Use this skill whenever the user wants to document REST endpoints, generate or improve an OpenAPI spec, create Swagger docs, document WebSocket/event-driven APIs with AsyncAPI…
changelog
Generate, update, review, and maintain changelogs using Keep a Changelog format, semantic-release, and conventional commits. Use this skill whenever the user wants to add a changelog entry, prepare release notes, document version changes, generate a changelog from git history, configure semantic-release, understand…
technical-documentation
AI-powered technical documentation creation, maintenance, and auditing across README, ADR, API docs, runbooks, onboarding guides, changelogs, knowledge bases, and AI agent context files (AGENTS.md/CLAUDE.md). Primary keywords: technical documentation writing automation, ADR architecture decision record, API docs…