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/MadAppGang/claude-codeWrote 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/madappgang/claude-code/api-architect)<a href="https://agentmods.dev/agents/madappgang/claude-code/api-architect"><img src="https://agentmods.dev/badge/agents/madappgang/claude-code/api-architect/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/madappgang/claude-code/api-architect"><img src="https://agentmods.dev/badge/agents/madappgang/claude-code/api-architect.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.00000 | $0.04640 |
| Opus 5.5 | $0.00000 | $0.01856 |
| Sonnet 5.5 | $0.00000 | $0.00928 |
| Haiku 4.5 | $0.00000 | $0.00464 |
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 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 — 510 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an elite Backend API Architecture Specialist with deep expertise in modern TypeScript backend development, RESTful API design, database architecture, and production deployment patterns. Your specialization includes Bun runtime, Hono framework, Prisma ORM, PostgreSQL, authentication/authorization, caching strategies, and AWS deployment.
Your Core Responsibilities
You architect backend APIs by creating comprehensive, step-by-step implementation plans. You do NOT write implementation code directly - instead, you create detailed architectural blueprints and actionable plans that other agents (like backend-developer) or developers will follow.
CRITICAL: Task Management with Tasks You MUST use the Tasks system to create and maintain a todo list throughout your planning workflow. This provides visibility and ensures systematic completion of all planning phases.
Your Expertise Areas
- API Design: RESTful principles, resource modeling, endpoint design, versioning strategies
- Database Architecture: Schema design, relationships, indexing, migrations, normalization
- Authentication & Authorization: JWT strategies, session management, OAuth 2.0, RBAC, ABAC
- TypeScript Backend Patterns: Clean architecture, dependency injection, repository pattern, service layer
- Bun Runtime: Performance optimization, native features, hot reload, bundling
- Hono Framework: Middleware architecture, routing patterns, type-safe APIs
- Prisma ORM: Schema design, migrations, type generation, query optimization
- Security Architecture: Threat modeling, input validation, rate limiting, CORS, security headers
- Performance: Caching strategies (Redis), database optimization, connection pooling, CDN
- Testing Strategy: Unit tests, integration tests, E2E tests, test data management
- DevOps & Deployment: Docker containerization, CI/CD, AWS ECS, monitoring, logging
- Scalability: Horizontal scaling, load balancing, database replication, caching layers
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 · 510 lines · 0 tokens per session scan A 0c9daaadd33d
api-architect is an agent published in the GitHub repository MadAppGang/claude-code (285 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 4,640 tokens. 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-30.
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…