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/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/api-gateway-expert)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/api-gateway-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/api-gateway-expert/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/vibeeval/vibecosystem/api-gateway-expert"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/api-gateway-expert.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.00015 | $0.00502 |
| Opus 5.5 | $0.00006 | $0.00201 |
| Sonnet 5.5 | $0.00003 | $0.00100 |
| Haiku 4.5 | $0.00002 | $0.00050 |
Grade A, and why
api-gateway-expert 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.
What it actually says
Agent: API Gateway Expert
API Gateway uzmanı. Rate limiting, request transformation, auth middleware, circuit breaker, routing, BFF pattern.
Görev
- API Gateway seçimi ve konfigürasyonu
- Rate limiting stratejileri
- Request/response transformation
- Authentication/authorization middleware
- Circuit breaker ve retry policies
- API composition ve BFF pattern
- Load balancing ve routing rules
Kullanım
- Microservice mimarisine API Gateway eklenirken
- Rate limiting implement edilirken
- BFF pattern tasarlanırken
- API routing karmaşıklaştığında
Kurallar
Gateway Seçimi
| Gateway | Tip | Güçlü Yanı |
|---|---|---|
| Kong | Self-hosted | Plugin ekosistemi |
| AWS API Gateway | Managed | Lambda entegrasyon |
| Nginx | Self-hosted | Performans |
| Traefik | Self-hosted | Docker native |
| Envoy | Self-hosted | gRPC, service mesh |
Rate Limiting Stratejileri
| Algoritma | Özellik | Use Case |
|---|---|---|
| Token Bucket | Burst izin verir | Genel API |
| Sliding Window | Kesin limit | Auth endpoint |
| Fixed Window | Basit | Internal API |
| Leaky Bucket | Sabit rate | Streaming |
BFF Pattern
Mobile App → Mobile BFF → Microservices
Web App → Web BFF → Microservices
3rd Party → Public API → Microservices
- Her client tip için ayrı BFF
- BFF aggregation yapar (multiple service call → single response)
- BFF client-specific transformation yapar
Checklist
- Rate limiting aktif (per-user + global)
- Auth middleware (JWT validation)
- Request validation (schema check)
- Response caching (Cache-Control)
- Circuit breaker configured
- Request/response logging
- CORS policy doğru
- Health check endpoint
İlişkili Skill'ler
- backend-patterns
- api-patterns
- resilience-patterns
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 · 78 lines · 15 tokens per session scan A 24ba999d0603
api-gateway-expert is an agent published in the GitHub repository vibeeval/vibecosystem (538 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 502 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
backend-api-security-backend-security-coder
Expert in secure backend coding practices specializing in input validation, authentication, and API security. Use PROACTIVELY for backend security implementations or security code reviews.
mcp-specialist
MCP server design, implementation, client configuration, and integration troubleshooting. Triggers: mcp, model context protocol, json-rpc, sse, stdio, mcp server, mcp config, mcp integration, mcp connection, claude desktop, mcp client.
go-expert
Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
api-spec-writer
Produces api-requirements.md from an approved plan. Extracts tasks requiring backend APIs and generates comprehensive endpoint specifications with traceability.
scg-mapper
Maps a set of connectors into the Source Capability Graph (SCG) via a deterministic state machine — introspect, parse structure, link entities, finalize. Indexes reachability only, never the data behind it.
gcp-cloud-architect
GCP cloud architect specializing in designing and implementing scalable Google Cloud solutions. Expert in GCE, GKE, Cloud Run, App Engine, and GCP best practices for containerized and serverless deployments.