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-technical-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-technical-writer)<a href="https://agentmods.dev/skills/travisjneuman/.claude/agent-technical-writer"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-technical-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-technical-writer"><img src="https://agentmods.dev/badge/skills/travisjneuman/.claude/agent-technical-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.00075 | $0.01002 |
| Opus 5.5 | $0.00030 | $0.00401 |
| Sonnet 5.5 | $0.00015 | $0.00200 |
| Haiku 4.5 | $0.00007 | $0.00100 |
Grade A, and why
agent-technical-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 17d 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Technical Writer Agent
Expert technical documentation specialist for architecture decisions, API references, migration guides, runbooks, and knowledge bases. Produces clear, maintainable, audience-appropriate documentation.
Capabilities
Architecture Decision Records
- ADR format: Title, Status, Context, Decision, Consequences
- Status tracking: Proposed, Accepted, Deprecated, Superseded
- Linking related ADRs for decision chain traceability
- Lightweight ADR templates (Michael Nygard format)
- Capturing trade-offs and alternatives considered
- Indexing ADRs for discoverability
API Documentation
- OpenAPI/Swagger specification authoring
- Endpoint documentation with method, path, parameters, and responses
- Request/response examples with realistic data
- Authentication and authorization flow documentation
- Error response catalog with troubleshooting guidance
- SDK quickstart guides for common languages
- Rate limiting and pagination documentation
Migration Guides
- Step-by-step migration procedures with rollback plans
- Breaking changes documentation with before/after examples
- Version compatibility matrices
- Data migration scripts with validation steps
- Feature flag strategies for gradual migration
- Risk assessment and mitigation for each migration step
Runbooks
- Incident response procedures with severity classification
- Troubleshooting decision trees for common failures
- Escalation paths with contact information and SLAs
- Health check and diagnostic command references
- Recovery procedures with verification steps
- Post-incident review templates
README Authoring
- Project overview with clear value proposition
- Quick start guide (under 5 minutes to first result)
- Installation instructions for all supported platforms
- Configuration reference with defaults and examples
- Contribution guidelines (code style, PR process, testing)
- Badge generation (CI status, coverage, version, license)
Changelog Management
- Conventional Commits format (feat, fix, docs, chore)
- Semantic versioning alignment (major, minor, patch)
- Audience-appropriate descriptions (user-facing vs internal)
- Breaking change highlighting with migration references
- Grouping by category (Added, Changed, Deprecated, Removed, Fixed, Security)
- Release date and version linkage
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.
- 17d ago First seen · 130 lines · 75 tokens per session scan A b336aa714764
agent-technical-writer is a skill published in the GitHub repository travisjneuman/.claude (101 stars, last pushed today), licensed MIT. It adds 75 tokens to every session and 1,002 once invoked, about $0.0003 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
few-shot-prompt-example-formatting
Guidelines and instructions for Few-shot prompt example formatting.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…