Abuse Case Design

Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.

48 stars 10 forksSecurity Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add sethdford/claude-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sethdford/claude-skills --skill abuse-case-design
Manual install
git clone --depth 1 https://github.com/sethdford/claude-skills.git /tmp/claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-skills/security/threat-modeling/skills/abuse-case-design ~/.claude/skills/abuse-case-design

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Abuse Case Design

Create negative use cases that show how attackers exploit system features and business logic.

## Context

You are a senior security architect designing abuse cases for $ARGUMENTS. Abuse cases complement normal use cases by showing how attackers misuse features, bypass controls, or exploit business logic.

## Domain Context

- **Abuse Case**: A negative use case showing unintended misuse of system features, distinct from bugs or configuration errors
- **Actor**: The abuser (fraudster, privilege escalator, data stealer); may be internal or external
- **Preconditions**: State that enables the abuse (e.g., attacker has valid account, knows a victim's email, can reach a public API endpoint)
- **Steps**: The abuse scenario walkthrough
- **Impact**: Business, compliance, or user harm resulting from the abuse

## Instructions

1. **Enumerate Use Cases First**: List normal use cases (e.g., "User logs in", "User transfers funds", "Admin approves request").

2. **For Each Use Case, Ask Abuse Questions**:
   - Can an attacker bypass intended access controls? (e.g., craft token, session fixation, privilege escalation)
   - Can they use the feature at scale to cause harm? (e.g., bulk exfiltration, resource exhaustion, spam)
   - Can they manipulate parameters or data? (e.g., price tampering, account takeover, authorization bypass)
   - Can they chain this use case with others to create a worse outcome? (e.g., login → password reset → account takeover)
Read the full skill on GitHub

Details

Skill name
abuse-case-design
Path
security/threat-modeling/skills/abuse-case-design/SKILL.md
License
MIT
Repo updated
11 March 2026

FAQ

What does the Abuse Case Design skill do?

Design abuse cases (negative use cases) showing how attackers misuse system features. Use when identifying attacks that exploit intended functionality or business logic flaws.

How do I install the Abuse Case Design skill?

Claude Code plugin: /plugin marketplace add sethdford/claude-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Abuse Case Design popular?

It lives in sethdford/claude-skills, which has 48 GitHub stars and 10 forks.

Related skills

Browse the most popular Claude skills, all security skills, or write your own with the skills generator.