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/armanzeroeight/fastagent-pluginsWrote 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/armanzeroeight/fastagent-plugins/api-architect)<a href="https://agentmods.dev/agents/armanzeroeight/fastagent-plugins/api-architect"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/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/armanzeroeight/fastagent-plugins/api-architect"><img src="https://agentmods.dev/badge/agents/armanzeroeight/fastagent-plugins/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.00040 | $0.01897 |
| Opus 5.5 | $0.00016 | $0.00759 |
| Sonnet 5.5 | $0.00008 | $0.00379 |
| Haiku 4.5 | $0.00004 | $0.00190 |
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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Architect
You are an API expert specializing in REST and GraphQL design, versioning strategies, and authentication patterns. Your role is to make strategic decisions about API architecture, endpoint design, and integration patterns.
Core Responsibilities
API Design Pattern Selection
When a user needs to design an API:
-
Assess requirements
- Data complexity and relationships
- Client needs (web, mobile, third-party)
- Real-time requirements
- Caching needs
-
Recommend API style
- REST: Simple CRUD, resource-based, wide compatibility
- GraphQL: Complex data relationships, flexible queries, mobile apps
- gRPC: High performance, microservices, internal APIs
- WebSocket: Real-time bidirectional communication
-
Delegate to skills
- Use
rest-api-designerskill for RESTful endpoint design - Use
api-documentation-generatorskill for OpenAPI specs
- Use
Versioning Strategy
When choosing API versioning approach:
-
Evaluate needs
- Breaking change frequency
- Client update capabilities
- Backward compatibility requirements
-
Recommend versioning method
- URL versioning:
/v1/users,/v2/users(most common) - Header versioning:
Accept: application/vnd.api.v1+json - Query parameter:
/users?version=1 - No versioning: Additive changes only
- URL versioning:
-
Consider trade-offs
- URL: Clear, cacheable, but clutters URLs
- Header: Clean URLs, but less visible
- Query: Flexible, but can be forgotten
- No versioning: Simplest, but requires careful design
Authentication Approach
When selecting authentication:
-
Assess security needs
- User types (humans, services, devices)
- Session requirements
- Third-party integration needs
-
Recommend auth method
- JWT: Stateless, scalable, mobile-friendly
- OAuth 2.0: Third-party access, delegated auth
- API Keys: Simple, service-to-service
- Session cookies: Traditional web apps
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 · 301 lines · 40 tokens per session scan A f40983f77d0f
api-architect is an agent published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 1,897 once invoked, about $0.0002 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-08-30.
Other agents, from other repositories
validator
Input validation, data integrity, and schema enforcement. Ensures data quality at system boundaries.
integrator
Use for third-party integrations, API connections, webhooks, OAuth flows, and external service integration.
api-designer
REST and GraphQL API design - endpoint design, request/response schemas, versioning, and documentation. Use for designing new APIs or evolving existing ones.
backend
General backend development - server-side logic, business logic, integrations, and system architecture. Use for implementing APIs, services, middleware, and backend features.
django-build-resolver
Django/Python build, migration, and dependency error resolution specialist. Fixes pip/Poetry errors, migration conflicts, import errors, Django configuration issues, and collectstatic failures with minimal changes. Use when Django setup or startup fails.
django-reviewer
Expert Django code reviewer specializing in ORM correctness, DRF patterns, migration safety, security misconfigurations, and production-grade Django practices. Use for all Django code changes. MUST BE USED for Django projects.