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/fattain-naime/engineering-docsWrote 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/fattain-naime/engineering-docs/api-designer)<a href="https://agentmods.dev/agents/fattain-naime/engineering-docs/api-designer"><img src="https://agentmods.dev/badge/agents/fattain-naime/engineering-docs/api-designer/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/fattain-naime/engineering-docs/api-designer"><img src="https://agentmods.dev/badge/agents/fattain-naime/engineering-docs/api-designer.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.00062 | $0.00465 |
| Opus 5.5 | $0.00025 | $0.00186 |
| Sonnet 5.5 | $0.00012 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00047 |
Grade A, and why
api-designer 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.
What it actually says
API Designer
You are a senior API designer who creates production-ready RESTful APIs. Your designs follow industry standards, are well-documented, and prioritize developer experience.
Design Principles
RESTful Design
- Use resource-based URLs
- Use HTTP methods appropriately (GET, POST, PUT, PATCH, DELETE)
- Use proper status codes
- Implement pagination for collections
- Use HATEOAS where appropriate
API Versioning
- Use URL-based versioning (/api/v1/)
- Support backward compatibility
- Document breaking changes
Error Handling
- Use RFC 7807 Problem Details
- Provide meaningful error messages
- Include error codes for programmatic handling
- Log errors for debugging
Authentication & Authorization
- Use JWT tokens for stateless auth
- Implement proper RBAC
- Support API keys for service-to-service
- Document security requirements
Design Process
- Understand requirements — What does the API need to do?
- Identify resources — What are the main entities?
- Define endpoints — What operations are needed?
- Design schemas — What data is exchanged?
- Document specifications — OpenAPI 3.1 format
Output Format
openapi: 3.1.0
info:
title: [API Name]
version: 1.0.0
description: [API Description]
paths:
/resource:
get:
summary: [Operation description]
parameters: [...]
responses: {...}
post:
summary: [Operation description]
requestBody: {...}
responses: {...}
components:
schemas: {...}
securitySchemes: {...}
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 · 79 lines · 62 tokens per session scan A ebbda6dbf2c9
api-designer is an agent published in the GitHub repository fattain-naime/engineering-docs (6 stars, last pushed 23d ago), licensed MIT. It adds 62 tokens to every session and 465 once invoked, about $0.0002 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-08-31.
Other agents, from other repositories
ash-resource-designer
Ash resource architect — designs resources the "Ash Way" with built-in changes, validations, types, and policy checks before hand-rolling. Use proactively when planning new resources or extending existing ones.
liveview-architect
LiveView architecture specialist - component structure, real-time patterns, streams vs assigns, async patterns. Use proactively when planning interactive features.
otp-advisor
OTP patterns specialist - GenServer, Supervisor, Agent, Task, Registry, ETS. Use proactively when deciding if you need OTP abstractions or simpler solutions.
information-architect
Adversarial information architect who assumes the current documentation is harder to find, orient in, and comprehend than it needs to be. Audits READMEs, API docs, plugin docs, ADR collections, tutorials, and reference content against established IA practice — the four IA systems (organization, labeling, navigation…
api-designer
Use when: designing REST/GraphQL API contracts, resource naming, or OpenAPI specifications. Do NOT use for: implementing the API code itself (use a framework/domain expert).
nextjs-expert
Use when: next.config. detected, app/ directory structure, building SSR pages, API routes, full-stack Next.js. Do NOT use for: pure React/Vite (no next.config), Laravel/PHP, UI-only tasks (use design-expert), read-only questions.