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 TheBeardedBearSAS/claude-craft --skill api-gatewaygit clone --depth 1 https://github.com/TheBeardedBearSAS/claude-craftWrote 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/thebeardedbearsas/claude-craft/api-gateway)<a href="https://agentmods.dev/skills/thebeardedbearsas/claude-craft/api-gateway"><img src="https://agentmods.dev/badge/skills/thebeardedbearsas/claude-craft/api-gateway.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00043 | $0.00459 |
| Opus 5 | $0.00022 | $0.00230 |
| Sonnet 5 | $0.00009 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
api-gateway 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 4d 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
API Gateway — Kong, Traefik, Patterns
API Gateway moderne pour routing, auth, rate limiting, observabilité.
Responsabilités
| Fonction | Outils |
|---|---|
| Routing (path, header, canary) | Kong, Traefik, Nginx |
| Auth (JWT, OAuth2, API keys) | Kong plugins, Traefik middleware |
| Rate Limiting (per-user/IP) | Redis-backed counters |
| Load Balancing | HAProxy, Traefik |
| Circuit Breaker | Resilience4j, Istio |
Stacks
Kong — Enterprise, plugins riches, K8s-native
Traefik — Cloud-native, auto-discovery
AWS API Gateway — Managed, serverless
Nginx — Performance max, self-hosted
Envoy — Service mesh (Istio), gRPC
Kong Config
services:
- name: payment-api
url: http://payment:8080
routes: [{ paths: ["/api/payments"] }]
plugins: [rate-limiting, jwt, prometheus]
Traefik Config
http:
routers:
payment:
rule: "PathPrefix(`/api/payments`)"
middlewares: [rate-limit, auth]
middlewares:
rate-limit:
rateLimit: { average: 100, burst: 50 }
Rate Limiting Algorithms
Fixed Window — Simple counter, bursty
Sliding Window — Rolling counter, lissé
Token Bucket — Flexible, burst toléré
Leaky Bucket — Output constant, strict
Pour setup : @devops-engineer
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.
- 4d ago First seen · 63 lines · 0 tokens per session scan A 824afc937040
api-gateway is a skill published in the GitHub repository TheBeardedBearSAS/claude-craft (105 stars, last pushed 5d ago), licensed MIT. It adds 43 tokens to every session and 459 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
edge-computing
Edge computing with Cloudflare Workers, Deno Deploy, Bun, Vercel Edge Functions, AWS Lambda@Edge, and edge databases (Turso, D1, DynamoDB Global Tables). Use when building low-latency edge applications, edge-side rendering, or globally distributed compute.
azure-servicebus-dotnet
Azure Service Bus SDK for .NET. Enterprise messaging with queues, topics, subscriptions, and sessions. Use for reliable message delivery, pub/sub patterns, dead letter handling, and background processing. Triggers: "Service Bus", "ServiceBusClient", "ServiceBusSender", "ServiceBusReceiver", "ServiceBusProcessor"…
sandbox-next
Build or maintain Cloudflare Sandbox apps on @cloudflare/sandbox@next (SDK 1.0 preview). Use sandbox-migrate-to-next when porting a stable app.
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
cloudflare
Discover and choose Cloudflare products for apps, APIs, AI agents, storage, networking, and security. Use for architecture and product selection, including when the user describes a need without naming a Cloudflare product; then find the relevant skill or documentation.