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 jeremylongworth-source/AgentSkills --skill rate-limit-designgit clone --depth 1 https://github.com/jeremylongworth-source/AgentSkillsWrote 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/jeremylongworth-source/agentskills/rate-limit-design)<a href="https://agentmods.dev/skills/jeremylongworth-source/agentskills/rate-limit-design"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/rate-limit-design/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/jeremylongworth-source/agentskills/rate-limit-design"><img src="https://agentmods.dev/badge/skills/jeremylongworth-source/agentskills/rate-limit-design.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.00055 | $0.00342 |
| Opus 5 | $0.00028 | $0.00171 |
| Sonnet 5 | $0.00011 | $0.00068 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
rate-limit-design 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 7d 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
Rate Limit Design
Core Workflow
- Identify protected resources, abuse cases, client types, tenants, plans, expected traffic, and operational constraints.
- Choose limit dimensions: user, tenant, token, IP, endpoint, method, workload, or account plan.
- Define algorithm and policy: fixed window, sliding window, token bucket, concurrency limit, quota, or adaptive control.
- Specify response headers, error contract, retry guidance, burst behavior, exemptions, and monitoring.
- Include rollout, tuning, and support override procedures.
- Add tests for allowed, limited, burst, and recovery behavior.
Safety Rules
- Do not invent production traffic, plan limits, or customer entitlements.
- Do not recommend limits that could silently block critical customer workflows without monitoring and support path.
- Escalate rate limits affecting billing, SLAs, compliance, security, or customer commitments.
Deliverable Shape
For rate-limit plans, provide:
- Protected resources and abuse cases
- Limit dimensions and policy
- Headers and error behavior
- Retry and burst guidance
- Monitoring and alerting
- Rollout and tuning plan
- Support override path
- Test cases
References
- Read
references/rate-limit-design-checklist.mdwhen designing or reviewing API rate limits.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 7d ago First seen · 47 lines · 55 tokens per session scan A 983f65e4413b
rate-limit-design is a skill published in the GitHub repository jeremylongworth-source/AgentSkills (1 stars, last pushed 8d ago), licensed MIT. It adds 55 tokens to every session and 342 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-09-03.
Other skills, from other repositories
authos-backend-integration
Secure backend APIs with AuthOS-issued JWTs and the AuthOS Node server adapter. Use when building an API that must verify AuthOS bearer tokens, enforce JWT claims, add Express middleware, validate JWKS keys, or create a backend-owned session after a browser OAuth callback.
authos-device-flow
Implement AuthOS device authorization for CLIs, TVs, and headless apps. Use when requesting device codes, building activation pages, polling /auth/token, handling MFA during device auth, or adding platform admin CLI login through AuthOS.
authos-rbac-control
Manage AuthOS organization members, roles, invitations, SCIM tokens, and capability-based permissions. Use when implementing team administration, custom roles, service access grants, invitation flows, SCIM provisioning, or authorization checks inside an AuthOS tenant.
authos-webhook-integration
Build AuthOS webhook receivers and manage tenant webhook subscriptions. Use when configuring organization webhooks, subscribing to event types, verifying live delivery signatures, testing delivery history, or using @drmhse/authos-node webhook helpers.
authos-service-api-integration
Integrate trusted backend services with AuthOS service API routes using X-Api-Key. Use when listing or managing service users, subscriptions, service metadata, service analytics, or provider-token requests from a server-side application.
authos-platform-deployment
Deploy and configure an AuthOS API instance from source or Docker. Use when setting database backend, JWT signing keys, environment variables, billing provider, SMTP, GeoIP, Docker images, health checks, or production reverse proxy settings.