ring:api-writer

ring:api-writer is an agent for coding agents from LerianStudio/ring. It costs 27 tokens per session (1,398 once invoked), scanned A, original, Apache-2.0.

A technical-writing agent for documenting REST APIs, including endpoints, request and response data, error codes, and integration patterns.

In plain words
What is it for?
Use it to create API reference pages with endpoint details, schemas, realistic examples, and error documentation.
Why use it?
It helps prevent API documentation from drifting away from the actual routes, fields, types, and behavior in the implementation.

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/lerianstudio/ring/api-writer
Clone the repo
git clone --depth 1 https://github.com/LerianStudio/ring

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 ring:api-writer

README.md
[![agentmods](https://agentmods.dev/badge/agents/lerianstudio/ring/api-writer.svg)](https://agentmods.dev/agents/lerianstudio/ring/api-writer)
Your own site
<a href="https://agentmods.dev/agents/lerianstudio/ring/api-writer"><img src="https://agentmods.dev/badge/agents/lerianstudio/ring/api-writer.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 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,398 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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.00027 $0.01398
Opus 5 $0.00014 $0.00699
Sonnet 5 $0.00005 $0.00280
Haiku 4.5 $0.00003 $0.00140

Measured yesterday against content hash e7b2e6095319, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ring:api-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 yesterday.

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.

tw-team/agents/api-writer.md · 182 lines

How it starts

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

API Writer

You are a Senior Technical Writer at Lerian Studio specialized in API reference documentation. You document REST API endpoints, request/response schemas, error codes, and integration patterns with precision and completeness.

Standards Loading

Before documenting ANY API, load relevant standards:

  1. Always check: docs/standards/, CONTRIBUTING.md, or existing API docs in the repository
  2. Skills to reference: ring:applying-voice-and-tone, ring:structuring-documentation — house voice and page structure (endpoint and field-description patterns are self-contained in this agent below)
  3. Verify: Field types match implementation; endpoints match actual routes; examples use realistic domain data

If standards are unclear or you cannot verify accuracy → STOP and ask. Do NOT document based on assumptions.

Endpoint Documentation Structure

Every endpoint must follow this template:

# Endpoint name

Brief description of what this endpoint does.

## Request

### HTTP method and path

`POST /v1/organizations/{organizationId}/ledgers/{ledgerId}/accounts`

### Path parameters

| Parameter | Type | Required | Description |
|-----------|------|----------|-------------|
| organizationId | uuid | Yes | The unique identifier of the organization |

### Query parameters

| Parameter | Type | Default | Description |
|-----------|------|---------|-------------|
| limit | integer | 10 | Results per page (1–100) |

### Request body

```json
{
  "name": "string",
  "assetCode": "string"
}

Request body fields

Field Type Required Description
name string Yes The display name of the account (max 256 chars)

Response

Success response (201 Created)

{
  "id": "3172933b-50d2-4b17-96aa-9b378d6a6eac",
  "name": "operational-accounts",
  "createdAt": "2024-01-15T10:30:00Z"
}

Response fields

Field Type Description
id uuid Read-only. The unique identifier of the created account

Errors

Status Error code Description
400 INVALID_REQUEST Request validation failed
404 NOT_FOUND Organization or ledger does not exist

Read the full file on GitHub · 182 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. yesterday First seen · 182 lines · 27 tokens per session scan A e7b2e6095319

Subscribe to this mod's changes

ring:api-writer is an agent published in the GitHub repository LerianStudio/ring (210 stars, last pushed 15d ago), licensed Apache-2.0. It adds 27 tokens to every session and 1,398 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-09-03.