ratelimit

Enforce Redis-backed sliding-window rate limits and quotas for API endpoints.

26|8|Updated Mar 19, 2026
One-click install
npx skills add https://github.com/arbazkhan971/godmode --skill ratelimit
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ratelimit
Source: https://github.com/arbazkhan971/godmode/tree/main/skills/ratelimit
Command: npx skills add https://github.com/arbazkhan971/godmode --skill ratelimit

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Enforces consistent rate limits and quota management across services to prevent abuse, reduce cost from excessive requests, and protect against brute-force and DDoS attacks.

Core Features & Use Cases

  • Atomic distributed counters via Redis Lua for accurate sliding-window or token-bucket enforcement across multiple instances.
  • Tiered plans, per-endpoint overrides, burst handling, long-term quotas with warnings, and fail-open graceful degradation when shared state is unavailable.
  • Use Case: Protect public API endpoints while allowing higher throughput for paid users, strict limits for auth endpoints, and unlimited internal service traffic.

Quick Start

Apply the ratelimit skill to audit and implement Redis-backed sliding-window counters and per-tier limits for the /api/* endpoints.

Frequently Asked Questions about ratelimit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enforce API rate limiting across multiple distributed instances?

API rate limiting across distributed instances is enforced using atomic Redis Lua counters, ensuring accurate sliding-window or token-bucket tracking. This synchronizes limit state across multiple web services to prevent abuse and control costs consistently.

What is the best way to apply different rate limits for anonymous and authenticated API traffic?

Differentiating anonymous and authenticated API traffic is handled through tiered plans and per-endpoint overrides. This allows strict limits for auth endpoints, higher throughput for paid users, and unlimited internal service traffic.

Does Redis sliding-window rate limiting handle sudden traffic bursts and long-term quotas?

Redis sliding-window rate limiting handles sudden traffic bursts and long-term quotas with warnings. It applies burst handling for immediate spikes and manages extended quota thresholds to prevent excessive requests over longer periods.

How do I implement fail-open fallback for API throttling when shared state is unavailable?

Fail-open fallback for API throttling is implemented to provide graceful degradation when shared state is unavailable. This ensures your distributed web services remain accessible during Redis connectivity issues rather than blocking all traffic.

How do I add standard RateLimit headers to API responses for quota management?

Standard RateLimit headers are added to every API response for quota management. This provides clients with transparent throttling metrics and monitoring data, ensuring they understand current usage limits and remaining request allowances.