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.
git clone --depth 1 https://github.com/LerianStudio/ringWrote 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/agents/lerianstudio/ring/api-writer)<a href="https://agentmods.dev/agents/lerianstudio/ring/api-writer"><img src="https://agentmods.dev/badge/agents/lerianstudio/ring/api-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/agents/lerianstudio/ring/api-writer"><img src="https://agentmods.dev/badge/agents/lerianstudio/ring/api-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.00027 | $0.01398 |
| Opus 5.5 | $0.00011 | $0.00559 |
| Sonnet 5.5 | $0.00005 | $0.00280 |
| Haiku 4.5 | $0.00003 | $0.00140 |
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 1mo 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 — 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:
- Always check:
docs/standards/,CONTRIBUTING.md, or existing API docs in the repository - 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) - 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 |
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.
- 1mo ago First seen · 182 lines · 27 tokens per session scan A e7b2e6095319
ring:api-writer is an agent published in the GitHub repository LerianStudio/ring (218 stars, last pushed 7d 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.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.
Other agents, from other repositories
api-contract-auditor
Internal dynos-work agent. Audits API, event, RPC, and schema contracts for compatibility, error semantics, and client/server drift. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:audit; never spawn this agent directly, from conversation, or outside a dynos-work task.
Backend Staff Engineer
Designs and reviews Node.js backend systems, reasoning about API contracts, caching, rate limiting, event-driven flows, and failure modes. Use for server logic, API design, queue consumers, resilience, or reliability work. Pairs with PostgreSQL Expert, who owns database internals and query planning.
geo-content-signals
Evaluates llms.txt quality, content chunkability, BLUF structure, heading quality, citation signals, and anti-patterns for GEO readiness.
seo-assets
Evaluates asset and structured data SEO dimensions: Open Graph, JSON-LD, images, and performance.
seo-content
Evaluates content SEO dimensions: internal linking, content quality, and GEO/AI readiness.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.