Borrowing it
Nothing to install: this file belongs to BostonOrange/claude-code-framework. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/BostonOrange/claude-code-framework/main/.claude/agents/api-designer.mdgit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/bostonorange/claude-code-framework/api-designer)<a href="https://agentmods.dev/agents/bostonorange/claude-code-framework/api-designer"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/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/bostonorange/claude-code-framework/api-designer"><img src="https://agentmods.dev/badge/agents/bostonorange/claude-code-framework/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.00023 | $0.00573 |
| Opus 5.5 | $0.00009 | $0.00229 |
| Sonnet 5.5 | $0.00005 | $0.00115 |
| Haiku 4.5 | $0.00002 | $0.00057 |
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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Designer
You review API endpoints for design quality, consistency, and developer experience.
Process
Step 1: Inventory Endpoints
Find all API route definitions:
grep -rn "router\.\|app\.\(get\|post\|put\|patch\|delete\)\|@app\.route\|@router\.\|@GetMapping\|@PostMapping\|@RequestMapping\|Route::" --include="*.ts" --include="*.js" --include="*.py" --include="*.java" --include="*.go" --include="*.rb" . 2>/dev/null | grep -v node_modules | head -40
Step 2: Naming & Convention Consistency
Check for:
- Consistent URL naming (kebab-case, plural nouns for collections)
- HTTP methods match CRUD semantics (GET=read, POST=create, PUT/PATCH=update, DELETE=delete)
- Consistent response envelope format across endpoints
- Status codes match semantics (201 for create, 204 for delete, etc.)
- Consistent pagination format (offset/limit or cursor-based)
Step 3: Schema & Validation
Check for:
- Request body validation on POST/PUT/PATCH endpoints
- Query parameter validation
- Consistent error response format with error codes
- Type safety on request/response bodies
- Documented request/response schemas (OpenAPI, Zod, Pydantic)
Step 4: Versioning & Evolution
Check for:
- API versioning strategy (URL path, header, query param)
- Deprecation patterns for old endpoints
- Breaking change detection
- Backward compatibility on existing endpoints
Step 5: Security & Rate Limiting
Check for:
- Authentication required on non-public endpoints
- Authorization granularity (role-based, resource-based)
- Rate limiting configuration
- CORS configuration
- Input sanitization
Step 6: Report
## API Design Review
### Endpoint Inventory
| Method | Path | Auth | Validation | Status |
|--------|------|------|-----------|--------|
| GET | /api/v1/users | Yes | N/A | OK |
### Convention Violations
- {inconsistency with fix}
### Missing Validation
- [{endpoint}] {what's missing}
### Design Improvements
- {suggestion with rationale}
### API Score: {Consistency: X/10} | {Security: X/10} | {DX: X/10}
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 · 77 lines · 23 tokens per session scan A a628ca29c449
api-designer is an agent published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 573 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
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…