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.
npx skills add roedyrustam/vibes-plug --skill api-gateway-proxy-expertgit clone --depth 1 https://github.com/roedyrustam/vibes-plugWrote 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/skills/roedyrustam/vibes-plug/api-gateway-proxy-expert)<a href="https://agentmods.dev/skills/roedyrustam/vibes-plug/api-gateway-proxy-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/api-gateway-proxy-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/skills/roedyrustam/vibes-plug/api-gateway-proxy-expert"><img src="https://agentmods.dev/badge/skills/roedyrustam/vibes-plug/api-gateway-proxy-expert.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 40 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00056 | $0.01126 |
| Opus 5 | $0.00028 | $0.00563 |
| Sonnet 5 | $0.00011 | $0.00225 |
| Haiku 4.5 | $0.00006 | $0.00113 |
Grade A, and why
api-gateway-proxy-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 9d 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 — 82 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Gateway & Reverse Proxy Expert
English
Description
A comprehensive guide for routing, load balancing, and managing traffic at the perimeter of your microservices architecture. Covers configuring API Gateways (Kong, Tyk), modern reverse proxies (Traefik, Caddy, NGINX), and understanding Service Mesh patterns.
Trigger Conditions
- When architecting a microservices backend that needs a unified entry point (BFF - Backend for Frontend).
- When configuring SSL/TLS termination, rate limiting, or IP allowlisting at the infrastructure level.
- When the user asks about "Traefik", "NGINX config", "Kong", or "API routing".
- When implementing blue-green deployments or canary releases via traffic splitting.
Core Architectural Guidelines
1. API Gateway Pattern
Instead of client applications calling individual microservices, route all traffic through an API Gateway.
- Cross-Cutting Concerns: Offload authentication (JWT verification), rate limiting, and CORS handling to the Gateway.
- Routing: Use path-based routing (e.g.,
/api/users-> Users Service,/api/billing-> Billing Service).
2. Tool Selection
- Traefik: Best for Docker/Kubernetes environments due to its auto-discovery capabilities via labels/annotations.
- Caddy: Best for simplicity and automatic HTTPS (Let's Encrypt provisioning).
- Kong API Gateway: Best for enterprise environments requiring extensive plugins (OIDC, rate limiting, analytics).
- Cloudflare (Edge): Use Cloudflare rules for edge-level caching, WAF, and DDoS protection before traffic even reaches your origin proxy.
3. Configuration Best Practices
- Timeouts: Always configure strict proxy read/write timeouts to prevent stalled connections from exhausting worker pools.
- Health Checks: Configure active health checks so the proxy can automatically remove failing backend instances from the load balancer pool.
- X-Forwarded Headers: Ensure your proxy correctly sets
X-Forwarded-ForandX-Forwarded-Protoso backend services know the client's real IP and protocol.
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.
- 9d ago First seen · 82 lines · 56 tokens per session scan A 56513dc48405
api-gateway-proxy-expert is a skill published in the GitHub repository roedyrustam/vibes-plug (49 stars, last pushed yesterday), licensed MIT. It adds 56 tokens to every session and 1,126 once invoked, about $0.0003 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 skills, from other repositories
api-and-interface-design
Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.
api-design
Design and review intuitive, scalable, maintainable HTTP APIs. Use this skill whenever the user wants to design a new REST API, review an existing API or spec, write OpenAPI 3.x definitions, or work with HTTP semantics (GET/POST/PUT/PATCH/DELETE), status codes, idempotency (Idempotency-Key), error envelopes (RFC 7807…
microservices-patterns
Decompose systems into microservices and apply canonical distributed-systems patterns. Use this skill whenever the user wants to split a monolith into services, design service boundaries, choose between microservices and a modular monolith, implement sagas or the outbox pattern, set up CQRS or event sourcing…
ddd
Domain-Driven Design system for software development. Use when designing new systems with DDD principles, refactoring existing codebases toward DDD, generating code scaffolding (entities, aggregates, repositories, domain events), facilitating Event Storming sessions, creating bounded context maps, or performing code…
fastify-best-practices
A reference guide for building Fastify, a Node.js framework for web servers and REST APIs, with JavaScript or TypeScript. It covers routes, plugins, validation, errors, testing, logging, security, databases, and deployment.
java-coding-standards
Java coding standards for Spring Boot services: naming, immutability, Optional usage, streams, exceptions, generics, and project layout.