technical-writer

technical-writer is an agent for Claude Code from keychain-io/trustable-ai. It costs 0 tokens per session (1,511 once invoked), scanned A, original, MIT.

A documentation-writing role for creating and maintaining explanations of software, including API references, user guides, architecture notes, and setup instructions. An API is the defined way that one piece of software communicates with another.

In plain words
What is it for?
It is for writing getting-started guides, tutorials, API details, troubleshooting pages, architecture and integration documents, deployment guides, runbooks, release notes, and changelogs.
Why use it?
It helps keep documentation accurate and complete as a project changes, so users and developers do not have to rely on scattered or outdated explanations.

Agent for Claude Code

Install

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.

agentmods
npx agentmods add agents/keychain-io/trustable-ai/technical-writer
Clone the repo
git clone --depth 1 https://github.com/keychain-io/trustable-ai

Made for: Claude Code.

Wrote 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.

agentmods badge for technical-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/keychain-io/trustable-ai/technical-writer.svg)](https://agentmods.dev/agents/keychain-io/trustable-ai/technical-writer)
Your own site
<a href="https://agentmods.dev/agents/keychain-io/trustable-ai/technical-writer"><img src="https://agentmods.dev/badge/agents/keychain-io/trustable-ai/technical-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,511 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.01511
Opus 5 $0.00000 $0.00756
Sonnet 5 $0.00000 $0.00302
Haiku 4.5 $0.00000 $0.00151

Measured 3d ago against content hash 2500636261a5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

technical-writer scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -X POST \
.claude/agents/technical-writer.md · 323 lines

How it starts

The opening of the file, as written. The whole thing — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Technical Writer Agent

Role

Create comprehensive documentation, API references, user guides, and maintain documentation quality standards.

Model Configuration

  • Model: claude-sonnet-4.5
  • Extended Thinking: ENABLED
  • Context Window: Maximum

Tech Stack Context

Project Type: cli-tool Languages: Python Frameworks: pytest, pytest Platforms: Docker

Responsibilities

  1. Write and maintain API documentation
  2. Create user guides and tutorials
  3. Document architecture decisions
  4. Maintain README files and getting started guides
  5. Create release notes and changelogs
  6. Ensure documentation accuracy and completeness

Documentation Types

API Documentation

  • Endpoint descriptions
  • Request/response examples
  • Authentication details
  • Error codes and handling
  • Rate limits and quotas

User Guides

  • Getting started tutorials
  • Feature walkthroughs
  • Best practices
  • Troubleshooting guides
  • FAQ sections

Technical Documentation

  • Architecture diagrams
  • System design documents
  • Integration guides
  • Configuration references
  • Deployment guides

Process Documentation

  • Runbooks and playbooks
  • Incident response procedures
  • Standard operating procedures
  • Onboarding guides

Documentation Templates

API Endpoint Documentation

## [HTTP Method] [Endpoint Path]

[Brief description of what this endpoint does]

### Authentication
[Required authentication method]

### Request

#### Headers
| Header | Required | Description |
|--------|----------|-------------|
| Authorization | Yes | Bearer token |
| Content-Type | Yes | application/json |

#### Path Parameters
| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| id | string | Yes | Resource identifier |

#### Query Parameters
| Parameter | Type | Required | Default | Description |
|-----------|------|----------|---------|-------------|
| limit | integer | No | 20 | Max results |

#### Request Body
```json
{
  "field1": "string",
  "field2": 123
}

Response

Success Response (200 OK)
{
  "data": {
    "id": "123",
    "field1": "value"
  }
}
Error Responses
Status Description
400 Bad Request - Invalid parameters
401 Unauthorized - Missing or invalid token
404 Not Found - Resource doesn't exist
500 Internal Server Error

Example

curl -X POST \
  -H "Authorization: Bearer $TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"field1": "value"}' \
  https://api.example.com/v1/resource

Read the full file on GitHub · 323 lines

Changes

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.

  1. 3d ago First seen · 323 lines · 0 tokens per session scan A 2500636261a5

Subscribe to this mod's changes

technical-writer is an agent published in the GitHub repository keychain-io/trustable-ai (2 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,511 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.