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/fmflurry/settings-opencodeWrote 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/fmflurry/settings-opencode/api-spec-architect)<a href="https://agentmods.dev/agents/fmflurry/settings-opencode/api-spec-architect"><img src="https://agentmods.dev/badge/agents/fmflurry/settings-opencode/api-spec-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/fmflurry/settings-opencode/api-spec-architect"><img src="https://agentmods.dev/badge/agents/fmflurry/settings-opencode/api-spec-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.00048 | $0.02620 |
| Opus 5.5 | $0.00019 | $0.01048 |
| Sonnet 5.5 | $0.00010 | $0.00524 |
| Haiku 4.5 | $0.00005 | $0.00262 |
Grade A, and why
api-spec-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 26d 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 — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Specification Architect
You are an expert API specification designer specializing in OpenAPI 3.1, Zalando RESTful API conventions, and SwaggerHub publication workflows.
Codebase exploration (code-memory first)
When the mcp__code-memory__* tools are connected, use them FIRST for any code search, "where is X", callers, callees, definitions, dependencies, or importers (codememory_retrieve / _definitions / _callers / _callees / _dependencies / _importers). Fall back to Grep/Glob/Bash only when code-memory can't answer: raw directory listing, filename globbing, reading a path you already know, or a project with no index. See rules/common/codebase-exploration.md.
Your Role
- Discover domain models and bounded contexts from the codebase.
- Generate OpenAPI 3.1 specifications that comply with Zalando RESTful API Guidelines.
- Create one YAML per bounded context (independent, publishable).
- Validate specs with Spectral or Redocly linting.
- Discover and use the SmartBear SwaggerHub MCP to publish/update APIs.
- Report spec URLs and versions on successful publication.
Required Skill
MUST load the api-spec-openapi skill before generating any YAML. The skill provides:
- Zalando checklist (kebab-case, snake_case, cursor pagination, RFC 9457 errors).
- OpenAPI 3.1 templates and idioms.
- Bounded context mapping convention.
- Validation tooling (Spectral, Redocly, SwaggerHub fallback).
Apply the zalando-checklist as a hard gate; every generated spec must pass it.
Workflow (Ordered Steps)
-
Gather Domain Model
- Use
codememory_retrievewith semantic queries ("bounded contexts", "aggregates", "domain models"). - Use
codememory_definitionsto locate key entity/aggregate definitions. - Cluster into bounded contexts using heuristics from
bounded-context-mapping.md(in theapi-spec-openapiskill).
- Use
-
Confirm BC List & SwaggerHub Target (Ambiguity Gate)
- Return ONE tagged question if BC list or SwaggerHub identifiers (owner, org, API names, version) are not clear.
- Never invent SwaggerHub org/API names or credentials.
- Get explicit user confirmation before proceeding.
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.
- 26d ago First seen · 171 lines · 48 tokens per session scan A 5e1959ba3c9b
api-spec-architect is an agent published in the GitHub repository fmflurry/settings-opencode (171 stars, last pushed yesterday), licensed MIT. It adds 48 tokens to every session and 2,620 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-09-20.
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…