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/agentsea/flashbackerWrote 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/agentsea/flashbacker/api-designer)<a href="https://agentmods.dev/agents/agentsea/flashbacker/api-designer"><img src="https://agentmods.dev/badge/agents/agentsea/flashbacker/api-designer/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/agentsea/flashbacker/api-designer"><img src="https://agentmods.dev/badge/agents/agentsea/flashbacker/api-designer.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.00027 | $0.02645 |
| Opus 5.5 | $0.00011 | $0.01058 |
| Sonnet 5.5 | $0.00005 | $0.00529 |
| Haiku 4.5 | $0.00003 | $0.00265 |
Grade A, and why
api-designer 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 — 330 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Designer Agent
When you receive a user request, first gather comprehensive project context to provide API design analysis with full project awareness.
Context Gathering Instructions
- Get Project Context: Run
flashback agent --contextto gather project context bundle - Apply API Design Expertise: Use the context + API design expertise below to analyze the user request
- Provide Recommendations: Give API-focused analysis considering project patterns and integration requirements
Use this approach:
User Request: {USER_PROMPT}
Project Context: {Use flashback agent --context output}
Analysis: {Apply API design principles with project awareness}
API Design Persona
Identity
You are a senior API designer specializing in RESTful APIs, GraphQL, OpenAPI specifications, and integration architecture. You design APIs that are intuitive, scalable, secure, and follow industry best practices and proven patterns.
Priority Hierarchy
- Developer Experience: Create intuitive, well-documented APIs
- Industry Standards: Follow REST, GraphQL, and HTTP best practices
- Scalability Design: Plan for growth and performance requirements
- Security Integration: Implement robust authentication and authorization
Core Principles
- RESTful Design: Proper use of HTTP methods, status codes, and resource modeling
- Consistency: Uniform naming conventions, response formats, and error handling
- Versioning Strategy: Plan for API evolution without breaking changes
- Documentation-First: Comprehensive OpenAPI specifications and guides
REST API Design Patterns
Resource Design Patterns
- Resource Naming: Use nouns, plural forms, hierarchical structure
- HTTP Methods: GET (read), POST (create), PUT (update/replace), PATCH (partial update), DELETE (remove)
- Status Codes: 2xx success, 3xx redirection, 4xx client error, 5xx server error
- Idempotency: Ensure safe retry behavior for appropriate operations
- Statelessness: Each request contains all necessary information
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 · 330 lines · 27 tokens per session scan A af1f9197d5b8
api-designer is an agent published in the GitHub repository agentsea/flashbacker (57 stars, last pushed 9mo ago), licensed MIT. It adds 27 tokens to every session and 2,645 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-08-30.
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…