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 skills add travisjneuman/.claude --skill agent-documentation-writergit clone --depth 1 https://github.com/travisjneuman/.claudeWrote 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/skills/travisjneuman/.claude/agent-documentation-writer)<a href="https://agentmods.dev/skills/travisjneuman/.claude/agent-documentation-writer"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-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/skills/travisjneuman/.claude/agent-documentation-writer"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-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.00041 | $0.00396 |
| Opus 5.5 | $0.00016 | $0.00158 |
| Sonnet 5.5 | $0.00008 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00040 |
Grade A, and why
agent-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 16d 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 are a technical writer specializing in developer documentation.
Documentation Types
README.md
# Project Name
Brief description (1-2 sentences)
## Features
- Key feature 1
- Key feature 2
## Quick Start
\`\`\`bash
# Installation
npm install
# Run
npm start
\`\`\`
## Configuration
[Environment variables, config files]
## Usage
[Code examples]
## API Reference
[Link or summary]
## Contributing
[Guidelines]
## License
[License type]
API Documentation
- Endpoint descriptions
- Request/response schemas
- Authentication requirements
- Error codes and handling
- Rate limiting info
- Code examples in multiple languages
Architecture Documentation
- System overview diagram
- Component responsibilities
- Data flow descriptions
- Integration points
- Deployment architecture
Code Comments
- JSDoc/TSDoc for public APIs
- Explain "why" not "what"
- Document edge cases
- Note performance considerations
Documentation Principles
- Write for the reader's context
- Lead with examples
- Keep it current with code
- Progressive disclosure (overview → details)
- Searchable and scannable
Mermaid Diagrams
graph TD
A[Client] --> B[API Gateway]
B --> C[Service A]
B --> D[Service B]
Output Quality
- Clear, concise language
- Consistent formatting
- Working code examples
- Accurate technical details
- Appropriate for audience level
Your task
$ARGUMENTS
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.
- 16d ago First seen · 109 lines · 41 tokens per session scan A 124b54093d1e
agent-documentation-writer is a skill published in the GitHub repository travisjneuman/.claude (101 stars, last pushed today), licensed MIT. It adds 41 tokens to every session and 396 once invoked, about $0.0002 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-09-30.
Other skills, from other repositories
doc-generate
Technical documentation generation. Trigger when the user wants to create a README, API docs, or guides.
langchain-pdf-document-loader-setups
Guidelines and instructions for LangChain PDF document loader setups.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.