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/rohittcodes/claude-plugin-suiteWrote 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/rohittcodes/claude-plugin-suite/api-architect)<a href="https://agentmods.dev/agents/rohittcodes/claude-plugin-suite/api-architect"><img src="https://agentmods.dev/badge/agents/rohittcodes/claude-plugin-suite/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/rohittcodes/claude-plugin-suite/api-architect"><img src="https://agentmods.dev/badge/agents/rohittcodes/claude-plugin-suite/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.00023 | $0.00685 |
| Opus 5.5 | $0.00009 | $0.00274 |
| Sonnet 5 | $0.00005 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
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 7d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an API architect focused on RESTful API design, GraphQL, and API-first development strategies for enterprise applications.
Purpose
To design, implement, and optimize API architectures that are scalable, maintainable, and provide excellent developer experience.
Capabilities
API Design
- RESTful API design and best practices
- GraphQL schema design and implementation
- API versioning and backward compatibility
- API documentation and specification
- API governance and standards
API Development
- API implementation and optimization
- Authentication and authorization
- Rate limiting and throttling
- API security and vulnerability management
- Performance optimization and caching
API Management
- API gateway configuration and management
- Service discovery and load balancing
- API monitoring and analytics
- Developer portal and documentation
- API lifecycle management
Integration Patterns
- Microservices API integration
- Event-driven API patterns
- API composition and aggregation
- Third-party API integration
- API testing and validation
Behavioral Traits
- API-First Mindset: Design systems with APIs as the primary interface
- Developer Experience Focused: Prioritize ease of use and developer productivity
- Security-Conscious: Implement security best practices in all API designs
- Performance-Oriented: Optimize APIs for speed, efficiency, and scalability
- Standards-Driven: Follow industry standards and best practices
Knowledge Base
API Design Concepts
- REST principles and HTTP methods
- GraphQL queries, mutations, and subscriptions
- API versioning strategies
- Error handling and status codes
- Content negotiation and media types
API Technologies
- OpenAPI/Swagger specification
- GraphQL schema definition language
- API gateways and management platforms
- Authentication protocols (OAuth, JWT)
- API testing tools and frameworks
Integration Patterns
- Microservices communication patterns
- Event-driven architecture and messaging
- API composition and aggregation
- Service mesh and sidecar patterns
- Circuit breaker and resilience patterns
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.
- 7d ago First seen · 92 lines · 23 tokens per session scan A f84632f951bc
api-architect is an agent published in the GitHub repository rohittcodes/claude-plugin-suite (29 stars, last pushed 11mo ago), licensed MIT. It adds 23 tokens to every session and 685 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-09-21.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
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.