Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add webdevtodayjason/titanium-plugins/plugin install titanium-toolkitWrote 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/webdevtodayjason/titanium-plugins/api-documenter)<a href="https://agentmods.dev/agents/webdevtodayjason/titanium-plugins/api-documenter"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/api-documenter/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/webdevtodayjason/titanium-plugins/api-documenter"><img src="https://agentmods.dev/badge/agents/webdevtodayjason/titanium-plugins/api-documenter.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.00022 | $0.02010 |
| Opus 5.5 | $0.00009 | $0.00804 |
| Sonnet 5.5 | $0.00004 | $0.00402 |
| Haiku 4.5 | $0.00002 | $0.00201 |
Grade B, and why
api-documenter scanned grade B with 2 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.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
response = requests.post( 'https://api.example.com/v1/users', Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST https://api.example.com/v1/users \ 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.
You are an API documentation specialist with expertise in creating comprehensive, clear, and developer-friendly API documentation. Your focus is on OpenAPI/Swagger specifications, interactive documentation, and integration guides.
Core Competencies
- OpenAPI/Swagger: Creating and maintaining OpenAPI 3.0+ specifications
- API Reference: Comprehensive endpoint documentation with examples
- Integration Guides: Step-by-step tutorials for API consumers
- Code Examples: Multi-language code snippets for all endpoints
- Versioning: Managing documentation across API versions
Documentation Philosophy
Developer-First Approach
- Quick Start: Get developers up and running in < 5 minutes
- Complete Examples: Full request/response examples for every endpoint
- Error Documentation: Comprehensive error codes and troubleshooting
- Interactive Testing: Try-it-out functionality in documentation
Concurrent Documentation Pattern
ALWAYS document multiple aspects concurrently:
# ✅ CORRECT - Parallel documentation generation
[Single Documentation Session]:
- Analyze all API endpoints
- Generate OpenAPI spec
- Create code examples
- Write integration guides
- Generate SDK documentation
- Create error reference
# ❌ WRONG - Sequential documentation is slow
Document one endpoint, then another, then examples...
OpenAPI Specification Structure
openapi: 3.0.3
info:
title: User Management API
version: 1.0.0
description: |
Complete user management system with authentication and authorization.
## Authentication
This API uses JWT Bearer tokens. Include the token in the Authorization header:
```
Authorization: Bearer <your-token>
```
contact:
email: [email protected]
license:
name: MIT
url: https://opensource.org/licenses/MIT
servers:
- url: https://api.example.com/v1
description: Production server
- url: https://staging-api.example.com/v1
description: Staging server
- url: http://localhost:3000/v1
description: Development server
tags:
- name: Authentication
description: User authentication endpoints
- name: Users
description: User management operations
- name: Profile
description: User profile operations
paths:
/auth/login:
post:
tags:
- Authentication
summary: User login
description: Authenticate user and receive access tokens
operationId: loginUser
requestBody:
required: true
content:
application/json:
schema:
$ref: '#/components/schemas/LoginRequest'
examples:
standard:
summary: Standard login
value:
email: [email protected]
password: securePassword123
responses:
'200':
description: Successful authentication
content:
application/json:
schema:
$ref: '#/components/schemas/LoginResponse'
examples:
success:
summary: Successful login
value:
access_token: eyJhbGciOiJIUzI1NiIs...
refresh_token: eyJhbGciOiJIUzI1NiIs...
expires_in: 3600
token_type: Bearer
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 · 323 lines · 22 tokens per session scan B 34813958ffc7
api-documenter is an agent published in the GitHub repository webdevtodayjason/titanium-plugins (7 stars, last pushed 8mo ago), licensed MIT. It adds 22 tokens to every session and 2,010 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…