dos

Analyze source code for denial of service threats mapped to STRIDE category D.

12|1|Updated Feb 9, 2026
One-click install
npx skills add https://github.com/florianbuetow/claude-code --skill dos
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dos
Source: https://github.com/florianbuetow/claude-code/tree/main/plugins/appsec/skills/dos
Command: npx skills add https://github.com/florianbuetow/claude-code --skill dos

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill identifies and helps you fix vulnerabilities that could lead to Denial of Service (DoS) attacks, ensuring your application remains available and resilient.

Core Features & Use Cases

  • Vulnerability Detection: Analyzes code for common DoS patterns like unbounded resource consumption, ReDoS, and missing rate limiting.
  • STRIDE Mapping: Aligns findings with the STRIDE threat model, specifically focusing on Availability risks.
  • Use Case: You've deployed a new API endpoint. Use this Skill to proactively scan the codebase for any potential DoS weaknesses before they can be exploited.

Quick Start

Use the dos skill to analyze the current file for denial of service vulnerabilities.

Frequently Asked Questions about dos

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

FAQPage Schema
How do I scan source code for denial of service vulnerabilities?

To scan source code for denial of service vulnerabilities, the Skill analyzes entry points and processing chains to identify unbounded resource consumption, missing rate limiting, and ReDoS patterns. It maps these availability risks directly to the STRIDE threat model.

What common ReDoS and resource exhaustion patterns should I look for in an API?

Common denial of service patterns include regular expression Denial of Service (ReDoS), unbounded input size handling, algorithmic complexity attacks, and decompression bomb risks. These vulnerabilities exploit synchronous blocking or uncontrolled resource allocation to exhaust system availability.

How do I check if my GraphQL endpoints are vulnerable to complexity attacks?

Checking GraphQL endpoints for complexity attacks involves analyzing query complexity issues and unbounded fan-out patterns within the code. The Skill identifies these availability risks by mapping resource consumption patterns back to the STRIDE framework.

Can I use this to find missing rate limiting and timeouts in asynchronous code paths?

Yes, you can use this to find missing rate limiting and timeouts in asynchronous code paths. The analysis detects synchronous blocking in async paths, connection exhaustion, and single points of failure that expose your application to availability threats.

Does this denial of service analysis require any specific security dependencies or tools?

This denial of service analysis requires no external dependencies or tools to function. It directly analyzes your source code's processing chains and resource consumption patterns to identify availability risks without needing additional security libraries.