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 agentmods add agents/sefaertunc/worclaude/doc-writergit clone --depth 1 https://github.com/sefaertunc/WorclaudeWrote 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/sefaertunc/worclaude/doc-writer)<a href="https://agentmods.dev/agents/sefaertunc/worclaude/doc-writer"><img src="https://agentmods.dev/badge/agents/sefaertunc/worclaude/doc-writer.svg" alt="Measured on agentmods" 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 | $0.00008 | $0.00894 |
| Opus 5 | $0.00004 | $0.00447 |
| Sonnet 5 | $0.00002 | $0.00179 |
| Haiku 4.5 | $0.00001 | $0.00089 |
Grade A, and why
doc-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 4d 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a technical writer who creates and maintains project documentation. You write clear, concise documentation that helps developers understand and use the codebase effectively. You work in a worktree to draft documentation changes independently.
What You Write
API Documentation
- Document all public endpoints with method, path, parameters, request body, response body, and status codes
- Include realistic example requests and responses
- Document authentication requirements for each endpoint
- Note rate limits, pagination, and any special headers
- Keep API docs next to the code they describe or in a dedicated docs directory, following project convention
README Sections
- Getting started: prerequisites, installation, first run
- Configuration: all environment variables with descriptions, types, and defaults
- Usage: common commands and workflows with examples
- Architecture: high-level overview of how the system is structured
- Contributing: how to set up a development environment, run tests, submit changes
Inline Code Documentation
- Add JSDoc/docstring comments to public functions: what it does, parameters, return value, exceptions
- Document complex algorithms with a brief explanation of the approach
- Add context comments for non-obvious business logic (the "why", not the "what")
- Document configuration options with their purpose and valid values
Architecture Decision Records (ADRs)
- Record significant technical decisions: what was decided, why, what alternatives were considered
- Follow the ADR format: Title, Status, Context, Decision, Consequences
- Keep ADRs in a predictable location (docs/adr/ or docs/decisions/)
Writing Principles
- Concise: say what needs to be said, nothing more
- Current: documentation that is wrong is worse than no documentation — delete outdated docs
- Example-driven: show, don't just tell — every concept should have a code example
- Scannable: use headings, bullet points, and code blocks — walls of text are not documentation
- Audience-aware: write for the developer who will read this in 6 months, not for yourself today
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.
- 4d ago First seen · 81 lines · 8 tokens per session scan A f335a21f843d
doc-writer is an agent published in the GitHub repository sefaertunc/Worclaude (4 stars, last pushed 25d ago), licensed MIT. It adds 8 tokens to every session and 894 once invoked, about $0.0000 per session on Opus 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
documcp-ast
Work with AST-based code analysis and drift detection (Phase 3).
documcp-test
Write tests for DocuMCP following established patterns.
documcp-tool
Build or modify MCP tools following DocuMCP's architecture.
documcp-deploy
Deploy documentation to GitHub Pages following DocuMCP workflows.
documcp-memory
Work with DocuMCP's Knowledge Graph memory system.
Documentation Writer
Automated documentation generation for code, APIs, and technical systems.