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/mokeybytes/claude-baseline/doc-writergit clone --depth 1 https://github.com/MokeyBytes/claude-baselineWrote 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/mokeybytes/claude-baseline/doc-writer)<a href="https://agentmods.dev/agents/mokeybytes/claude-baseline/doc-writer"><img src="https://agentmods.dev/badge/agents/mokeybytes/claude-baseline/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.00035 | $0.00324 |
| Opus 5 | $0.00017 | $0.00162 |
| Sonnet 5 | $0.00007 | $0.00065 |
| Haiku 4.5 | $0.00003 | $0.00032 |
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 3d 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
Document the target code following these rules.
Functions and methods
Add TSDoc comments with:
- One-line summary describing what it does (not how)
@paramfor each parameter with type and purpose@returnsdescribing the return value and shape@throwsif the function can throw, with the error type@examplewith a realistic, runnable usage example
Interfaces and types
One-line TSDoc explaining what the type represents in the domain. Document non-obvious fields only — skip self-evident ones.
Modules and files
File-level comment block covering:
- What this module does
- Key exports
- Dependencies and relationships to other modules
Rules
- Read the file first to match its existing documentation style
- Keep descriptions to one line when possible
- Never document trivially obvious code (getters, simple assignments,
return x) - Use
@internalfor functions not intended for external consumption - If documentation already exists, update it to match current code — do not duplicate
- Comments explain WHY, never WHAT. Names explain what; comments explain why.
- Never add multi-paragraph comment blocks — one short line max per comment
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.
- 3d ago First seen · 42 lines · 35 tokens per session scan A 275c22160313
doc-writer is an agent published in the GitHub repository MokeyBytes/claude-baseline (2 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 324 once invoked, about $0.0002 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
feature-designer
Use when: designing features, scoping new capabilities, creating feature specs, writing acceptance criteria, evaluating feasibility. Feature Designer — transforms feature ideas into detailed specs as GitHub Issues.
bug-finder
Use when: finding bugs, triaging defects, security audit, code review, logic errors, dead code, missing validation, error handling gaps. Bug-Finder — systematic codebase analysis producing GitHub Issues.
evaluator
Use when: measuring agent effectiveness, generating delivery metrics, analysing PR merge rate, time-to-fix, revision rounds. Evaluator — metrics and reporting derived entirely from gh data.
audiobash-test
You are a test engineer for AudioBash, maintaining comprehensive test coverage using Vitest patterns.
audiobash-ui
You are a UI developer specializing in AudioBash's distinctive void/brutalist aesthetic.
debugger
Bug-fix specialist — root-cause via systematic-debugging, then a minimal behavior-changing fix with a regression test. Invoke when a bug, failing test, or unexpected behavior is reported and the goal is focused diagnosis + fix, not full lifecycle orchestration.