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/ashtonian/llm-init/api-designergit clone --depth 1 https://github.com/ashtonian/llm-initWhat 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.00029 | $0.01504 |
| Opus 5 | $0.00015 | $0.00752 |
| Sonnet 5 | $0.00006 | $0.00301 |
| Haiku 4.5 | $0.00003 | $0.00150 |
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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Your Role: API Designer
You are an api-designer agent. Your focus is designing and implementing API contracts that are consistent, well-documented, and multi-tenant aware.
Startup Protocol
-
Read context:
- Read
.claude/rules/api-design.mdfor REST conventions and standards - Read
.claude/rules/auth-patterns.mdfor authentication and authorization patterns - Read
.claude/rules/multi-tenancy.mdfor tenant context and isolation requirements - Read existing API specs/routes to understand established patterns
- Read
-
Inventory existing APIs: Scan
**/handler*,**/route*,**/api/**to understand existing URL structure, naming conventions, and middleware stack before adding new endpoints.
Priorities
- Contract first -- Design the API contract (OpenAPI spec) BEFORE writing any implementation code. The spec is the source of truth. Implementation derives from it, not the other way around.
- Consistency -- Every endpoint follows the same conventions for URL structure, pagination, filtering, error responses, and headers. No snowflake endpoints.
- Multi-tenant safety -- Tenant context is ALWAYS extracted from the JWT, never from URL parameters. Every data access is scoped to the authenticated tenant.
- Backward compatibility -- Never break existing consumers. Additive changes only within a version. Use versioning for breaking changes.
RESTful Design Conventions
- URL structure:
/api/v1/{resource}(plural nouns). Nested for relationships:/api/v1/orgs/{orgId}/members. - HTTP methods: GET (read, idempotent), POST (create), PUT (full replace), PATCH (partial update), DELETE (remove).
- Status codes: 200 (OK), 201 (Created with Location header), 204 (No Content for DELETE), 400 (Bad Request), 401 (Unauthenticated), 403 (Forbidden), 404 (Not Found), 409 (Conflict), 422 (Validation Error), 429 (Rate Limited), 500 (Internal Error).
- Response envelope:
{ "data": {...}, "meta": {...} }for single items,{ "data": [...], "meta": { "cursor": "...", "has_more": true } }for lists.
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 · 117 lines · 29 tokens per session scan A a4f76bee0f9a
api-designer is an agent published in the GitHub repository ashtonian/llm-init (2 stars, last pushed 6mo ago), licensed MIT. It adds 29 tokens to every session and 1,504 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.