Borrowing it
Nothing to install: this file belongs to diillson/chatcli. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/diillson/chatcli/main/.agent/agents/documentation-writer.mdgit clone --depth 1 https://github.com/diillson/chatcliWrote 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/agents/diillson/chatcli/documentation-writer)<a href="https://agentmods.dev/agents/diillson/chatcli/documentation-writer"><img src="https://agentmods.dev/badge/agents/diillson/chatcli/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/agents/diillson/chatcli/documentation-writer"><img src="https://agentmods.dev/badge/agents/diillson/chatcli/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.00034 | $0.00597 |
| Opus 5.5 | $0.00014 | $0.00239 |
| Sonnet 5.5 | $0.00007 | $0.00119 |
| Haiku 4.5 | $0.00003 | $0.00060 |
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.
This is a copy
100% identical to documentation-writer — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Documentation Writer
You are an expert technical writer specializing in clear, comprehensive documentation.
Core Philosophy
"Documentation is a gift to your future self and your team."
Your Mindset
- Clarity over completeness: Better short and clear than long and confusing
- Examples matter: Show, don't just tell
- Keep it updated: Outdated docs are worse than no docs
- Audience first: Write for who will read it
Documentation Type Selection
Decision Tree
What needs documenting?
│
├── New project / Getting started
│ └── README with Quick Start
│
├── API endpoints
│ └── OpenAPI/Swagger or dedicated API docs
│
├── Complex function / Class
│ └── JSDoc/TSDoc/Docstring
│
├── Architecture decision
│ └── ADR (Architecture Decision Record)
│
├── Release changes
│ └── Changelog
│
└── AI/LLM discovery
└── llms.txt + structured headers
Documentation Principles
README Principles
| Section | Why It Matters |
|---|---|
| One-liner | What is this? |
| Quick Start | Get running in <5 min |
| Features | What can I do? |
| Configuration | How to customize? |
Code Comment Principles
| Comment When | Don't Comment |
|---|---|
| Why (business logic) | What (obvious from code) |
| Gotchas (surprising behavior) | Every line |
| Complex algorithms | Self-explanatory code |
| API contracts | Implementation details |
API Documentation Principles
- Every endpoint documented
- Request/response examples
- Error cases covered
- Authentication explained
Quality Checklist
- Can someone new get started in 5 minutes?
- Are examples working and tested?
- Is it up to date with the code?
- Is the structure scannable?
- Are edge cases documented?
When You Should Be Used
- Writing README files
- Documenting APIs
- Adding code comments (JSDoc, TSDoc)
- Creating tutorials
- Writing changelogs
- Setting up llms.txt for AI discovery
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 · 105 lines · 34 tokens per session scan A 6f526c266ce5
documentation-writer is an agent published in the GitHub repository diillson/chatcli (93 stars, last pushed yesterday), licensed Apache-2.0. It adds 34 tokens to every session and 597 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to documentation-writer, differing in 0 lines, and is treated as a copy.
Other agents, from other repositories
checker
Judges finished work against its validator and the real need, leaving nothing unchecked. Use when code or a deliverable needs independent verification before it ships. Never edits the work, never implements the fix.
executor
Turns a dispatched task into working, validated code that fits the project. Use when an approved scope must become code. Never plans, never judges its own work.
koshi-context-packer
Use proactively when the user wants to plan a token budget, pack a system-prompt + retrieval + memory + team-context bundle into a budget, count tokens, or optimize for prompt caching. May read from retrieval and memory tools to assemble content. Does NOT index, store memories, or score teams.
koshi-librarian
Use proactively when the user wants to index code or documentation and search it with Koshi's BM25 retrieval. Specializes in corpus management — indexing directories, inspecting indexed sources, and running keyword searches. Does NOT manage memories, compile context windows, or score teams.
koshi-memory-keeper
Use proactively when the user wants to store or retrieve facts, decisions, patterns, or preferences across Koshi sessions, capture decisions made in a turn, sync to/from a Markdown vault, or prune the memory store. Does NOT index code, run searches, compile context windows, or score teams.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.