sc-rate-limiting

Detect missing rate limiting and DoS vectors in web applications.

7|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/fatihkan/badi --skill sc-rate-limiting-fatihkan
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-rate-limiting
Source: https://github.com/fatihkan/badi/tree/main/.claude/skills/security-check/sc-rate-limiting
Command: npx skills add https://github.com/fatihkan/badi --skill sc-rate-limiting-fatihkan

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Missing rate limiting on sensitive endpoints exposes applications to denial-of-service vectors, including ReDoS, resource exhaustion, and unbounded queries.

Core Features & Use Cases

  • Detects missing rate limits on login, password reset, API key generation, file uploads, and other sensitive endpoints.
  • Identifies ReDoS patterns, unbounded query patterns, and potential resource exhaustion scenarios, with guidance to remediate.
  • Provides actionable findings and recommended mitigations for secure deployments.

Quick Start

Run the sc-rate-limiting skill against your web application to surface missing rate limits and potential DoS vectors.

Frequently Asked Questions about sc-rate-limiting

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

FAQPage Schema
How do I detect missing rate limits on sensitive web application endpoints?

Detect missing rate limits by scanning login, password reset, API key generation, and file upload endpoints. This identifies DoS vectors and resource exhaustion risks, providing structured findings with recommended mitigations for secure deployments.

How can I check my web services for ReDoS and pagination abuse vulnerabilities?

Check web services for ReDoS and pagination abuse by applying pattern checks to data endpoints and admin interfaces. This detects unbounded query patterns and resource exhaustion scenarios, yielding actionable findings to remediate risks.

What is the best way to identify denial-of-service vectors in my APIs?

Identify API denial-of-service vectors by analyzing authentication and data endpoints for unbounded queries and request size handling issues. This surfaces resource exhaustion risks and provides guidance to remediate them.

Does this rate limiting analysis work across both authentication and admin interfaces?

Yes, rate limiting analysis applies to web services and APIs across authentication, data endpoints, and admin interfaces. It detects missing throttle controls and resource exhaustion risks throughout the application architecture.

Why should I scan for unbounded query patterns and request size handling issues?

Scan for unbounded query patterns and request size issues to prevent resource exhaustion and denial-of-service attacks. This detects vulnerabilities in data endpoints and provides recommended mitigations for secure deployments.

When do I need to analyze my web application for resource exhaustion risks?

Analyze web applications for resource exhaustion risks when sensitive endpoints lack throttle controls. This surfaces missing rate limits on login and file upload endpoints, detecting ReDoS vectors and unbounded query patterns.