Rate limiting

Skill shinzoxD/knackbox/skills/coding/rate-limiting

Curated, auditable, benchmark-ready Agent Skills library for Claude Code, Codex, OpenCode, Cursor, and more.

Install

npx -y skills add shinzoxD/knackbox --skill rate-limiting

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

28 days oldThe repository was created 28 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Design rate limiting and throttling for APIs and gateways with fair use and abuse resistance. Use whenever the user asks about rate limits, quotas, 429 responses, token buckets, leaky buckets, or protecting endpoints from overload and abuse.

The file declares its own license as Apache-2.0. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.

SKILL.md

1.6 KB, 273 tokens by cl100k_base, as published. Nobody here has run it

Rate Limiting

Limits protect availability and fairness. Choose key (IP, user, API key, tenant), algorithm, and client-visible headers carefully.

Workflow

Threat: abuse, noisy neighbor, cost control, fair multi-tenant.
Dimension: per identity, per route, global.
Algorithm: fixed window, sliding, token bucket — trade accuracy vs cost.
Response: 429, Retry-After, rate limit headers.
Bypass/admin paths and authenticated vs anonymous.
Observability: reject rate, top offenders.
Edge vs app vs gateway placement.

Output format

## Rate limit design
**Goals:** …
**Keys:** …
**Limits:** …
**Algorithm:** …
**Client contract:** …
**Fail mode:** open vs closed

Rules

State fail-open vs fail-closed when the limiter store is down.
Do not rate-limit health checks into outages.
Document limits in API docs.
Prefer tenant-aware limits in B2B.
Avoid only IP limits behind shared NAT without care.

Edge cases

GraphQL: cost-based limits.
Webhooks outbound: separate egress budgets.
Login endpoints: stricter anti-bruteforce.