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 j4flmao/agent-skills --skill rate-limitinggit clone --depth 1 https://github.com/j4flmao/agent-skillsWrote 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/j4flmao/agent-skills/rate-limiting)<a href="https://agentmods.dev/skills/j4flmao/agent-skills/rate-limiting"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/rate-limiting/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/j4flmao/agent-skills/rate-limiting"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/rate-limiting.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00761 |
| Opus 5 | $0.00010 | $0.00380 |
| Sonnet 5 | $0.00004 | $0.00152 |
| Haiku 4.5 | $0.00002 | $0.00076 |
Grade A, and why
rate-limiting 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 8d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
rate-limiting
Purpose
Comprehensive description for rate-limiting providing detailed architectures and best practices.
Core Principles
- First principle - Reliability
- Second principle - Scalability
- Third principle - Maintainability
- Fourth principle - Security
- Fifth principle - Observability
Agent Protocol
Triggers: Code execution Input Context Required: Repository context Output Artifact: System design document Response Formats:
{ "status": "ok", "action": "completed" }
Decision Matrix
[Start] -> (Condition Check) -> [End]
|
v
[Alternative]
Detailed Architectural Overview
[Client] ---> [API Gateway] ---> [Microservice]
|
v
[Database]
Workflow Steps
Phase 1
- Initialization step 1
- Initialization step 2
- Initialization step 3
- Initialization step 4 Phase 2
- Processing step 1
- Processing step 2
- Processing step 3
- Processing step 4 Phase 3
- Storage step 1
- Storage step 2
- Storage step 3
- Storage step 4 Phase 4
- Retrieval step 1
- Retrieval step 2
- Retrieval step 3
- Retrieval step 4 Phase 5
- Optimization step 1
- Optimization step 2
- Optimization step 3
- Optimization step 4 Phase 6
- Cleanup step 1
- Cleanup step 2
- Cleanup step 3
- Cleanup step 4
Extended Troubleshooting Guide
| Symptom | Primary Cause | Mitigation Action |
|---|---|---|
| High Latency | Network Congestion | Scale up resources |
| Data Loss | Database Failure | Restore from backup |
| Connection Refused | Service Down | Restart service |
| Unauthorized Access | Invalid Token | Renew token |
| Out of Memory | Memory Leak | Optimize code |
| Disk Full | Log Overload | Rotate logs |
Complete Execution Scenario
[Trigger] -> [Analysis] -> [Action] -> [Result Verification]
Rules and Guidelines
- Always validate inputs.
- Ensure backward compatibility.
- Keep logs structured.
- Fail gracefully.
- Apply rate limiting where appropriate.
What ships with it
8 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.
- references/algorithms.md 5.6 KB
- references/backpressure.md 6.0 KB
- references/distributed-rate-limiting.md 4.6 KB
- references/implementation-patterns.md 4.7 KB
- references/rate-limiting-api-gateway.md 3.2 KB
- references/rate-limiting-implementations.md 5.9 KB
- references/rate-limiting-monitoring.md 3.4 KB
- references/rate-limiting-queuing.md 4.3 KB
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.
- 8d ago First seen · 123 lines · 21 tokens per session scan A 563026c2c961
rate-limiting is a skill published in the GitHub repository j4flmao/agent-skills (23 stars, last pushed 5d ago), licensed MIT. It adds 21 tokens to every session and 761 once invoked, about $0.0001 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
api-rate-limit-handler
Implement bounded, idempotency-aware API throttling, backoff, and retry handling for 429 and transient 5xx responses.
implementing-api-rate-limiting-and-throttling
Implements API rate limiting and throttling controls using token bucket, sliding window, and fixed window algorithms to protect against brute force attacks, credential stuffing, resource exhaustion, and API abuse. The engineer configures per-user, per-IP, and per-endpoint rate limits using Redis-backed counters, API…
detecting-api-enumeration-attacks
Detect and prevent API enumeration attacks including BOLA and IDOR exploitation by monitoring sequential identifier access patterns and authorization failures.
implementing-api-abuse-detection-with-rate-limiting
Implement API abuse detection using token bucket, sliding window, and adaptive rate limiting algorithms to prevent DDoS, brute force, and credential stuffing attacks.
implementing-api-gateway-security-controls
Implements security controls at the API gateway layer including authentication enforcement, rate limiting, request validation, IP allowlisting, TLS termination, and threat protection. The engineer configures API gateways (Kong, AWS API Gateway, Azure APIM, Apigee) to act as a centralized security enforcement point…
securing-api-gateway-with-aws-waf
Securing API Gateway endpoints with AWS WAF by configuring managed rule groups for OWASP Top 10 protection, creating custom rate limiting rules, implementing bot control, setting up IP reputation filtering, and monitoring WAF metrics for security effectiveness.