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 glincker/claude-code-marketplace --skill tech-writergit clone --depth 1 https://github.com/glincker/claude-code-marketplaceWrote 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/glincker/claude-code-marketplace/tech-writer)<a href="https://agentmods.dev/skills/glincker/claude-code-marketplace/tech-writer"><img src="https://agentmods.dev/badge/skills/glincker/claude-code-marketplace/tech-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.1 | $0.00023 | $0.01330 |
| Opus 5 | $0.00012 | $0.00665 |
| Sonnet 5 | $0.00005 | $0.00266 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
tech-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 7d 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 — 238 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tech Writer Agent
Professional technical documentation specialist. Creates comprehensive documentation that bridges the gap between technical teams and business stakeholders, developers and end-users.
Agent Expertise
- Technical documentation for developers
- User guides for non-technical audiences
- API documentation (OpenAPI/Swagger)
- Architecture decision records (ADRs)
- Onboarding documentation
- Release notes and changelogs
- Business-to-technical translation
- Documentation as Code practices
Key Capabilities
- Developer Documentation: API references, SDK guides, integration docs
- User Documentation: User guides, tutorials, FAQs, troubleshooting
- Business Documentation: Project proposals, technical requirements, RFCs
- API Documentation: Auto-generate OpenAPI specs from code
- Architecture Docs: System design, ADRs, technical specifications
- Cross-Functional Communication: Translate between business and technical language
Workflow
When activated, this agent will:
- Analyze codebase and project structure
- Identify documentation gaps
- Create appropriate documentation types
- Use clear, audience-appropriate language
- Include diagrams, code examples, and use cases
- Maintain consistent style and formatting
Quick Commands
# API documentation
"Generate API documentation from this Express app"
# User guide
"Create a user guide for this application"
# Technical specification
"Write a technical specification for this feature"
# Business translation
"Explain this technical implementation in business terms"
# Onboarding docs
"Create onboarding documentation for new developers"
# Architecture documentation
"Document the system architecture with diagrams"
# Release notes
"Generate release notes from recent changes"
Documentation Types
For Developers
API Documentation:
- REST API endpoints with examples
- GraphQL schema and queries
- SDK usage guides
- Code snippets and integration examples
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 238 lines · 23 tokens per session scan A ddb10ef12003
tech-writer is a skill published in the GitHub repository glincker/claude-code-marketplace (36 stars, last pushed 9mo ago), licensed Apache-2.0. It adds 23 tokens to every session and 1,330 once invoked, about $0.0001 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-30.
Other skills, from other repositories
documentation-writer
Write clear technical documentation including READMEs, API docs, architecture guides, and inline documentation. Use when creating or improving project documentation.
documentation-patterns
Technical documentation patterns for READMEs, ADRs, API docs (OpenAPI 3.1), changelogs, and writing style guides. Use when creating project documentation, writing architecture decisions, documenting APIs, or maintaining changelogs.
document-writer
Write or update technical documentation grounded in the real codebase. Use when the user asks for README, API docs, architecture guides, user guides, CONTRIBUTING docs, migration notes, or JSDoc/code comments, or wants technical docs rewritten into natural Chinese with correct terminology. Not for general prose…
documentation-standards
Use when writing README files, API documentation, user guides, or technical documentation following industry standards from Google, Microsoft, and GitLab style guides.
documentation
Technical writing, API docs, and documentation best practices.
Technical Documentation Writer
Write developer documentation that developers actually read. API docs, READMEs, architecture guides, and onboarding docs with clarity and structure.