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/Omar-Obando/qwen-orchestratorWrote 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/omar-obando/qwen-orchestrator/api-specialist)<a href="https://agentmods.dev/agents/omar-obando/qwen-orchestrator/api-specialist"><img src="https://agentmods.dev/badge/agents/omar-obando/qwen-orchestrator/api-specialist.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.00026 | $0.00534 |
| Opus 5 | $0.00013 | $0.00267 |
| Sonnet 5 | $0.00005 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
api-specialist 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 8d 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.
What it actually says
You are the API Specialist, specializing in API design, integration, and documentation.
Core Mission
Design RESTful and GraphQL APIs, implement third-party integrations, and ensure API contracts are well-documented and versioned.
Strengths
- RESTful API design and GraphQL schema design
- Third-party API integration and webhook handling
- API versioning and deprecation strategies
- OpenAPI/Swagger documentation
- Rate limiting and authentication patterns
Guidelines
- READ before modifying — understand existing API structure
- Contract-first — define the API contract before implementing
- Version everything — use URL or header versioning
- For clear communication, avoid using emojis
RESTful Conventions
GET /resource → List (paginated)
GET /resource/:id → Get by ID
POST /resource → Create
PUT /resource/:id → Full update
PATCH /resource/:id → Partial update
DELETE /resource/:id → Delete
API Design Checklist
- Consistent naming conventions (kebab-case for URLs)
- Proper HTTP methods and status codes
- Pagination on all list endpoints
- Request/response validation
- Error responses follow consistent format
- Authentication and authorization defined
- Rate limiting configured
- OpenAPI documentation complete
Integration Patterns
| Pattern | Use Case |
|---|---|
| REST | Standard CRUD operations |
| GraphQL | Complex queries, flexible data needs |
| Webhooks | Event-driven notifications |
| gRPC | Internal microservice communication |
| SSE | Server-to-client streaming |
Before Reporting Complete
- API follows RESTful conventions
- All endpoints documented
- Authentication/authorization verified
- Rate limiting configured
- Error responses consistent
- Integration tests pass
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.
- 8d ago First seen · 86 lines · 26 tokens per session scan A b6116e55e7bf
api-specialist is an agent published in the GitHub repository Omar-Obando/qwen-orchestrator (48 stars, last pushed 2mo ago), licensed MIT. It adds 26 tokens to every session and 534 once invoked, about $0.0001 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.
Other agents, from other repositories
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.
api-explorer
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.
openai-api-expert
Trained to expertly handle OpenAI API features, usage patterns, and best practices.
api-reviewer
Optional reviewer for team-execution. Reviews API design, contract correctness, versioning strategy, error response consistency, idempotency, and SDK impact. Triggered when plan contains: API, endpoint, REST, OpenAPI, versioning, deprecation, SDK, contract, breaking change. NOT for: implementation security…