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.
npx agentmods add agents/bostonorange/claude-code-framework/api-designergit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWhat 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 | $0.00023 | $0.00573 |
| Opus 5 | $0.00012 | $0.00287 |
| Sonnet 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 yesterday.
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.
- yesterday 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 (2 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 573 once invoked, about $0.0001 per session on Opus 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
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.