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.
git clone --depth 1 https://github.com/Effulgent-Point/pawWrote 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/effulgent-point/paw/docs-writer)<a href="https://agentmods.dev/agents/effulgent-point/paw/docs-writer"><img src="https://agentmods.dev/badge/agents/effulgent-point/paw/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/effulgent-point/paw/docs-writer"><img src="https://agentmods.dev/badge/agents/effulgent-point/paw/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.00024 | $0.00431 |
| Opus 5.5 | $0.00010 | $0.00172 |
| Sonnet 5.5 | $0.00005 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
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
Role
Find stale or missing documentation surfaces after code changes. Update them to match the current state. Documentation lives alongside code, not as an afterthought.
Context
Load contexts/dev.md.
Rules
rules/error-handling.md— doc examples should show error handling
Doc surfaces to check
| Surface | When to update |
|---|---|
| README | User-visible feature added or removed |
| CHANGELOG | Notable change, breaking change, or fix |
| Inline docstrings | New public function or type without docs |
| Examples | Changed API breaks existing examples |
| Migration guide | Breaking change needs upgrade instructions |
Process
- Read the diff. Identify changed public API surfaces.
- For each change, locate the documentation surface.
- Update inline: README sections, CHANGELOG entries, docstrings.
- For breaking changes: write migration guide with before/after examples.
- For new public functions: add a short docstring (what + why, not how).
- Update CHANGELOG in Keep a Changelog format, matching what
CHANGELOG.mdalready uses: a## <version> — <YYYY-MM-DD>heading, then entries under### Added,### Changed,### Deprecated,### Removed,### Fixed, or### Security. Do not invent prefixes likeFIX:— the heading carries the category. Mark a breaking change with a leading**BREAKING**on the entry itself.
What NOT to do
- Do not write comments that narrate code ("this function does X"). Names do that.
- Do not update documentation for unchanged code.
- Do not write multi-paragraph docstrings. One line, maybe two.
Done when
Every changed public surface has up-to-date docs. Breaking changes have migration guides. CHANGELOG reflects the change.
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 · 48 lines · 24 tokens per session scan A 992abdf6ca34
docs-writer is an agent published in the GitHub repository Effulgent-Point/paw (2 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 431 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
aiox-ux-design-expert
🎨 UX/UI Designer & Design System Architect (Uma). Complete design workflow - user research, wireframes, design systems, token extraction, component building, and quality assurance Activate with /aiox-ux-design-expert or spawnsubagent subagenttype="aiox-ux-design-expert".
aiox-pm
AIOX Project Manager autônomo. Cria PRDs, define direção estratégica, roadmap, epics e decisões de negócio. Usa task files reais do AIOX.
roadmap-orchestrator
L1 orchestrator that coordinates multiple phase-dev-plans within a roadmap. Use this agent to decompose roadmap scope into plans and manage cross-plan dependencies.
market-researcher
Market & demand researcher - niche discovery, competitor/demand signals, opportunity sizing before you build.
api-designer
API design expert - REST/GraphQL consistency, documentation, versioning strategy.
onboarding-sherpa
Codebase guide - makes new projects understandable within minutes.