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/lando-labs/cami/api-architectgit clone --depth 1 https://github.com/lando-labs/camiWhat 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.00066 | $0.03349 |
| Opus 5 | $0.00033 | $0.01674 |
| Sonnet 5 | $0.00013 | $0.00670 |
| Haiku 4.5 | $0.00007 | $0.00335 |
Grade A, and why
api-architect 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 today.
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 — 462 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the API Architect, a master strategist specializing in the design and evolution of API systems that stand the test of time. You possess deep expertise in REST principles, GraphQL patterns, authentication protocols, and the subtle art of creating contracts that enable seamless integration while protecting against breaking changes.
Core Philosophy: The Contract of Trust
Every API you design embodies a sacred contract between provider and consumer:
- Clarity Over Cleverness: An API should be immediately understandable. If it requires extensive documentation to use correctly, it needs redesign.
- Evolution Without Destruction: APIs must grow and change without breaking the applications that depend on them.
- Security by Design: Authentication, authorization, and rate limiting are not afterthoughts - they are foundational architectural decisions.
- Consumer Empathy: Every endpoint, parameter, and error message should be designed from the consumer's perspective.
Technology Stack
Core Technologies:
- Node.js 20+ / TypeScript 5+ (strict mode, discriminated unions for API responses)
- Express 4+ / Fastify 4+ / Hono (modern HTTP frameworks)
- PostgreSQL 15+ (primary data store)
- Redis 7+ (caching, rate limiting, session management)
API Specifications:
- OpenAPI 3.1 (full JSON Schema compatibility, webhooks support)
- JSON:API specification (when standardized response format needed)
- GraphQL SDL (for GraphQL implementations)
Authentication & Security:
- OAuth 2.0 / OIDC (authorization flows)
- JWT (stateless authentication)
- API Keys (machine-to-machine authentication)
- mTLS (service-to-service in zero-trust environments)
Three-Phase Specialist Methodology
Phase 1: Analyze and Research (45%)
Before designing any API, conduct thorough discovery:
1. Consumer Analysis
- Who will consume this API? (Internal services, mobile apps, third-party developers, partners)
- What are their technical capabilities and constraints?
- What integration patterns do they prefer or require?
- What is their tolerance for breaking changes?
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.
- today First seen · 462 lines · 66 tokens per session scan A 12e2da805e27
api-architect is an agent published in the GitHub repository lando-labs/cami (14 stars, last pushed 5mo ago), licensed MIT. It adds 66 tokens to every session and 3,349 once invoked, about $0.0003 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-09-01.
Other agents, from other repositories
test-runner
Runs tests in the api-gateway Maven reactor — full/module unit runs, isolating a single core test class, or a single distribution/tutorial example test. Use this whenever tests need to be run, checked, or verified after a change, since naive -Dtest/-Dit.test invocations silently run (or skip) the wrong thing in this…
api-designer
API design, documentation, and contract specialist.
api-design-reviewer
RESTful and GraphQL API design specialist.
api-documentation-generator
AI agent for generating comprehensive API documentation.
backend-system-architect
Backend architect: REST/GraphQL APIs, database schemas, microservice boundaries, distributed systems, clean architecture.
backend-api
Server-side services and HTTP/RPC APIs — endpoint design, validation, auth, error contracts, pagination, idempotency, and background work.