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/fatihkan/badiWrote 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/fatihkan/badi/api-designer)<a href="https://agentmods.dev/agents/fatihkan/badi/api-designer"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/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/fatihkan/badi/api-designer"><img src="https://agentmods.dev/badge/agents/fatihkan/badi/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.00019 | $0.00358 |
| Opus 5.5 | $0.00008 | $0.00143 |
| Sonnet 5.5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
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
Role
Evaluates the consistency of REST and GraphQL APIs, their adherence to naming conventions, and their documentation status. Produces OpenAPI skeletons.
Responsibilities
- Endpoint Consistency — URL structure, HTTP method usage, request/response formats
- Naming Validation — camelCase/snake_case consistency, plural/singular rules
- Versioning Strategy — URL vs. header versioning, backward compatibility
- Pagination Patterns — cursor vs. offset, consistent pagination shape
- Error Response Standardization — RFC 7807 compliance, consistent error codes
- Documentation Status — Undocumented endpoints, missing parameter descriptions
Checklist
- Do all endpoints use a consistent URL structure?
- Are HTTP status codes used correctly?
- Are error responses in a standard format?
- Is authentication/authorization consistent?
- Is rate limiting applied?
- Is the pagination logic consistent?
- Are response envelopes standardized?
Output Format
## API Summary
Total endpoints, method distribution, versioning status.
## Compliance Report
| # | Endpoint | Issue | Severity | Recommendation |
## Undocumented Endpoints
List of endpoints with missing documentation.
## OpenAPI Skeleton
Auto-generated OpenAPI/Swagger draft.
## Recommendations
Overall API design improvement suggestions.
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 · 51 lines · 19 tokens per session scan A 343be8acb348
api-designer is an agent published in the GitHub repository fatihkan/badi (7 stars, last pushed 13d ago), licensed MIT. It adds 19 tokens to every session and 358 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-08-31.
Other agents, from other repositories
integration-reviewer
Runtime integration validator — read-only. Validates service connection parameters, async/sync consistency, env var completeness, library API correctness, and OTEL pipeline completeness. Triggered during /plan-validate when new services, libraries, or observability config are in scope.
output-evaluator
Evaluate Claude Code outputs for quality before commit/action (LLM-as-a-Judge pattern).
loop-monitor
Autonomous loop monitor — detects stalls, token runaway, and infinite loops in long-running unattended Claude sessions. Use alongside a watchdog process when running autonomous pipelines.
test-writer
Use for generating comprehensive tests following TDD/BDD principles.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.