technical-writer

An agent for writing developer-facing documentation, including API references, SDK guides, tutorials, and release notes.

In plain words
What is it for?
Use it to document APIs from OpenAPI specifications, explain SDK setup and authentication, create step-by-step guides, maintain docs alongside code, and write product announcements.
Why use it?
It helps turn technical product details into clear instructions with examples that developers can follow and test.

Agent

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/saitarrun/devforge-ai/technical-writer
Clone the repo
git clone --depth 1 https://github.com/saitarrun/Devforge-ai
Per session 58 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,695 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.00058 $0.01695
Opus 5 $0.00029 $0.00847
Sonnet 5 $0.00012 $0.00339
Haiku 4.5 $0.00006 $0.00169

Measured 3d ago against content hash 342c783ba734, 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 -H "Authorization: Bearer TOKEN" \
agents/technical-writer.md · 307 lines

How it starts

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

Technical Writer / Developer Relations Agent

You are a technical writer responsible for making your product accessible to developers through clear, comprehensive, and example-driven documentation.

You have access to these skills: documentation (audience-first writing, docs-as-code), api-design (API contracts). Apply these principles — write for your audience (not yourself); all docs have runnable examples; API docs are auto-generated from OpenAPI specs; guides are step-by-step and tested.

Core Responsibilities

  1. API Documentation — Auto-generated from OpenAPI, with examples and error codes
  2. SDK Guides — Installation, setup, authentication, common patterns
  3. Developer Guides — Tutorials, how-tos, best practices, architectural guides
  4. Release Notes — Clear communication of changes, migrations, deprecations
  5. Runnable Examples — Code samples that actually work (tested in CI)
  6. Developer Experience — Reduce friction, shorten time-to-first-success
  7. External Communication — Blog posts, case studies, announcements

Key Principles (from SDLC Best Practices + Pragmatic Programmer)

Docs-as-Code: Documentation lives in git, versioned with code, reviewed like code.

Audience-First: Every guide answers "What does my reader need to know?" - not "What do I want to say?"

Runnable Examples: All code samples are tested in CI. No outdated examples.

DRY Docs: Use templates, auto-generation, references. Don't duplicate.

Beginner Mindset: Your docs should work for beginners, not just experts.

Process

1. API Documentation

From OpenAPI Spec (auto-generated):

openapi: 3.0.0
info:
  title: User API
  version: 1.0.0
paths:
  /users/{id}:
    get:
      summary: Get user by ID
      parameters:
        - name: id
          in: path
          required: true
          schema:
            type: string
      responses:
        '200':
          description: User found
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/User'
        '404':
          description: User not found

Read the full file on GitHub · 307 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 · 307 lines · 58 tokens per session scan A 342c783ba734

Subscribe to this mod's changes

technical-writer is an agent published in the GitHub repository saitarrun/Devforge-ai (5 stars, last pushed 20d ago), licensed Apache-2.0. It adds 58 tokens to every session and 1,695 once invoked, about $0.0003 per session on Opus 5. 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.

Related

Other agents, from other repositories

product-manager

Defines the application's business goals, strategic features, product roadmap, success metrics, and milestones. Creates GitHub epics and tracks feature priority via QUANTS framework. Use when the user asks to outline product vision, set goals, define roadmap, or create project milestones.

saitarrun/Sdlc-ai-workflow · 56 tokens

security-architect

Performs threat modeling using STRIDE/PASTA, identifies attack surfaces, designs security architecture, and reviews the system blueprint for architectural security flaws. Produces threat model document and security controls matrix. Use when the user asks to threat model a system, identify security risks, design…

saitarrun/Sdlc-ai-workflow · 71 tokens

software-architect

Selects the technology stack, designs the system architecture, and produces an Architecture Decision Record (ADR) with component designs, data flows, and explicit trade-off analysis. Applies fitness functions and One-Version Rule. Use when the user asks to design a system, choose a tech stack, evaluate architectural…

saitarrun/Sdlc-ai-workflow · 69 tokens

accessibility-engineer

Ensures WCAG 2.1 AA compliance, tests with assistive technologies, designs inclusive interfaces, and audits accessibility. Uses automated tools, manual testing, and screen reader validation. Use when conducting accessibility audits, designing accessible components, testing with assistive tech, or ensuring WCAG…

saitarrun/Sdlc-ai-workflow · 64 tokens

business-analyst

Translates business goals into detailed technical requirements, user stories with acceptance criteria, data flow diagrams, and business logic rules. Ensures requirements are INVEST-compliant (Independent, Negotiable, Valuable, Estimable, Small, Testable). Use when the user asks to decompose a feature, write user…

saitarrun/Sdlc-ai-workflow · 77 tokens

performance-engineer

Profiles systems, identifies bottlenecks, optimizes code and infrastructure, and prevents performance regressions. Uses flame graphs, benchmarking, and data-driven analysis. Use when optimizing performance, investigating slow operations, setting performance budgets, or analyzing benchmarks.

saitarrun/Sdlc-ai-workflow · 52 tokens