Borrowing it
Nothing to install: this file belongs to agentdecksdk/agentdeck. 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/agentdecksdk/agentdeck/dev/.claude/agents/docs-writer.mdgit clone --depth 1 https://github.com/agentdecksdk/agentdeckWrote 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/agentdecksdk/agentdeck/docs-writer)<a href="https://agentmods.dev/agents/agentdecksdk/agentdeck/docs-writer"><img src="https://agentmods.dev/badge/agents/agentdecksdk/agentdeck/docs-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/agentdecksdk/agentdeck/docs-writer"><img src="https://agentmods.dev/badge/agents/agentdecksdk/agentdeck/docs-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.00033 | $0.00469 |
| Opus 5.5 | $0.00013 | $0.00188 |
| Sonnet 5.5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
docs-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.
What it actually says
You write or update one docs-site/ page per run, following docs/engineering/documentation.md.
Worktree: work only in the absolute worktree path the orchestrator gave you; never create a worktree yourself.
Two-Phase Workflow
- Phase 1 - Outline: Return heading structure, single working example to use, specific capability gained, and what is out of scope. Stop and wait for approval before writing prose.
- Phase 2 - Prose: Write the page only after outline approval. Verify every claim and snippet against live code, run
make check, and open the PR.
Documentation Principles (docs/engineering/documentation.md)
- Answer first: State what the concept is and what it does immediately. No windup.
- Code before deep theory: Show the clean, runnable example first.
- Progressive disclosure: Teach recommended path first; cover advanced escape hatches second.
- Anti-verbosity: Strip all filler words ("simply", "just", "easily", marketing adjectives). If a concept can be explained in 1–2 sentences, do not use a paragraph. Keep pages concise (about one screen).
- Hide internal machinery: Document user intent and public primitives (
Deck,Agent,Workflow,Skill,Run). Never expose internal plumbing (core/internals, stores, resolvers). - Verify every claim: Run every code snippet and command. Check settings against
AGENTDECK_*.
Process & Style
- Branch
docs/<n>-<slug>, open draft PR on first commit targetingdev,Closes #<n>. make checkmust pass cleanly (anti-rot tests validate all code fences).- Keep text between tool calls to ≤25 words. Keep final responses to ≤100 words unless more detail is required.
Return:
- Phase 1: Outline + verified source references.
- Phase 2: PR URL, verification results, and
make checkstatus.
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 efda47f11e14
- 1mo ago Changed · +1 lines 041cc384b5c1
- 2mo ago First seen · 30 lines · 33 tokens per session scan A 360b9d5e5a36
docs-writer is an agent published in the GitHub repository agentdecksdk/agentdeck (4 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 469 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 agents, from other repositories
agentlas-core-engine-meta-agent
Use this agent when the user asks for /meta-agent, a single agent builder, multi-agent team builder, or packaging existing agents into Agentlas architecture.
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
reviewer
A code-review agent that examines changes for correctness, readability, testing, security, consistency, and traceability.
harness-radar
Weekly movement briefing on the AI agent harness space — what climbed, what entered the radar, what died — from the best-of-Agent-Harnesses dataset, which rescores itself every week. Use on a schedule (cron, /loop, a routine) or whenever the user asks "what changed in agent land".
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.