api-architect

An architecture advisor for web APIs, the interfaces that let applications exchange data. It covers REST, GraphQL, gRPC, and WebSocket designs, along with versioning and authentication.

In plain words
What is it for?
Use it when planning endpoints, choosing between API patterns, deciding how to version an API, or designing authentication.
Why use it?
It helps choose an API style and structure that fit the clients, data, real-time needs, and compatibility requirements.

Agent

Install

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.

agentmods
npx agentmods add agents/armanzeroeight/fastagent-plugins/api-architect
Clone the repo
git clone --depth 1 https://github.com/armanzeroeight/fastagent-plugins
Per session 40 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,897 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00040 $0.01897
Opus 5 $0.00020 $0.00949
Sonnet 5 $0.00008 $0.00379
Haiku 4.5 $0.00004 $0.00190

Measured yesterday against content hash f40983f77d0f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

plugins/api-toolkit/agents/api-architect.md · 301 lines

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:

  1. Assess requirements

    • Data complexity and relationships
    • Client needs (web, mobile, third-party)
    • Real-time requirements
    • Caching needs
  2. 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
  3. Delegate to skills

    • Use rest-api-designer skill for RESTful endpoint design
    • Use api-documentation-generator skill for OpenAPI specs

Versioning Strategy

When choosing API versioning approach:

  1. Evaluate needs

    • Breaking change frequency
    • Client update capabilities
    • Backward compatibility requirements
  2. 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
  3. 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:

  1. Assess security needs

    • User types (humans, services, devices)
    • Session requirements
    • Third-party integration needs
  2. 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

Read the full file on GitHub · 301 lines

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.

  1. yesterday First seen · 301 lines · 40 tokens per session scan A f40983f77d0f

Subscribe to this mod's changes

api-architect is an agent published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 1mo ago), licensed MIT. It adds 40 tokens to every session and 1,897 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-08-30.