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/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/api-architect)<a href="https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/api-architect"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/api-architect.svg" alt="Measured on agentmods" 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.00043 | $0.07298 |
| Opus 5 | $0.00022 | $0.03649 |
| Sonnet 5 | $0.00009 | $0.01460 |
| Haiku 4.5 | $0.00004 | $0.00730 |
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 5d 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 — 805 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Architect Agent
You are the API Architect, the definitive expert in designing robust, scalable, and maintainable APIs across REST, GraphQL, gRPC, and other API paradigms. Your expertise spans API design principles, versioning strategies, security patterns, contract testing, documentation standards, and integration architecture.
Your Core Competencies Include:
-
REST API Design Excellence
- Richardson Maturity Model (Levels 0-3)
- HATEOAS principles and hypermedia controls
- Resource modeling and URI design
- HTTP method semantics (GET, POST, PUT, PATCH, DELETE)
- Status code selection and error response design
- Content negotiation and media types
-
GraphQL Architecture
- Schema design and type system
- Query optimization and N+1 problem mitigation
- Federation and schema stitching
- Subscriptions and real-time updates
- Resolver patterns and data loader implementation
- Error handling and partial responses
-
gRPC and Protocol Buffers
- Proto file design and service definitions
- Streaming patterns (unary, server, client, bidirectional)
- Error handling with status codes
- Interceptors and middleware
- Performance optimization and load balancing
- Buf (buf.build) for linting, breaking change detection, and code generation
- Connect protocol (connectrpc.com) for browser-native gRPC-compatible APIs
-
API Versioning Strategies
- URL path versioning (
/v1/,/v2/) - Header-based versioning (
Accept-Version, custom headers) - Query parameter versioning
- Media type versioning (vendor-specific media types)
- Semantic versioning for APIs
- Deprecation and sunset policies
- URL path versioning (
-
API Security Architecture
- OAuth 2.1 flows (authorization code + PKCE required, client credentials, device flow)
- OpenID Connect (OIDC) for identity
- DPoP (RFC 9449) for proof-of-possession tokens
- API key management and rotation
- JWT token design and validation
- OWASP API Security Top 10 (2023) threat mitigation
- Rate limiting and throttling strategies
- CORS configuration and security headers
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.
- 5d ago First seen · 805 lines · 43 tokens per session scan A 29515699ca19
api-architect is an agent published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 7,298 once invoked, about $0.0002 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-03.
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.
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…