Business Logic Testing
Use when testing application-specific workflow and business-rule flaws that scanners cannot find — price/quantity/parameter tampering, workflow and state-machine bypass, race conditions and TOCTOU, replay, and abuse of coupons/refunds/limits. Requires understanding what the app is supposed to do.
Install
/plugin marketplace add mn-youssef/security-skillsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add mn-youssef/security-skills --skill business-logic-testinggit clone --depth 1 https://github.com/mn-youssef/security-skills.git /tmp/security-skills
mkdir -p ~/.claude/skills
cp -r /tmp/security-skills/skills/business-logic-testing ~/.claude/skills/business-logic-testingPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Business Logic Testing (FIND/EXPLOIT — the pro's bread and butter) ## Overview Find flaws in *what the app allows*, not *how it's coded*. These are valid requests that produce invalid outcomes — buying for $0, refunding twice, skipping a required step. No scanner finds them because each is unique to your business rules. **Core principle:** The app enforces the *intended* flow; you test every *unintended* path that still "works." Think: "what does this feature assume, and what if I break that assumption?" ## Applies when / Skip when - **Applies when:** the app has multi-step workflows, money/credits/quotas, stateful processes, or business rules that can be abused. - **Skip when:** it's a stateless single-action utility with no rules or state → N/A (rare — most apps have *some* logic; double-check before skipping). - **If N/A:** report "business-logic-testing: N/A — no stateful workflow/rules" and stop. ## ⚠️ Authorization Your own app/test data. Logic abuse can move money/state — use a non-production environment. ## Method 1. **Understand the intended flow** — map the steps, the rules, and the assumptions at each step (order: add → pay → ship; rule: qty ≥ 1; assumption: price comes from the server). 2. **Challenge each assumption** — negative/zero/huge values, skipped steps, reordered steps, client-supplied values the server should own, repeated actions. 3. **Attack the state machine** — reach states out of order or revisit terminal states.
Details
- Skill name
business-logic-testing- Repository
- mn-youssef/security-skills
- Path
skills/business-logic-testing/SKILL.md- License
- MIT
- Repo updated
- 12 June 2026
FAQ
What does the Business Logic Testing skill do?
Use when testing application-specific workflow and business-rule flaws that scanners cannot find — price/quantity/parameter tampering, workflow and state-machine bypass, race conditions and TOCTOU, replay, and abuse of coupons/refunds/limits. Requires understanding what the app is supposed to do.
How do I install the Business Logic Testing skill?
Claude Code plugin: /plugin marketplace add mn-youssef/security-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Business Logic Testing popular?
It lives in mn-youssef/security-skills, which has 49 GitHub stars and 7 forks.
Related skills
Access Control Testing
49mn-youssef/security-skills
Use when testing whether users can access data or actions they shouldn't — IDOR/BOLA, horizontal and vertical privilege escalation, multi-tenant isolation, forced browsing, function-level authorization (BFLA), and mass assignment. The #1 cause of real-world breaches.
Active Pentest
49mn-youssef/security-skills
Use when you need to actually run security tests against a running application you own or are authorized to test — the shared execution harness for lab/proxy/scanner setup, safe non-destructive execution, and standardized proof-of-concept capture that the find/exploit specialist skills rely on.
API Security Testing
49mn-youssef/security-skills
Use when testing REST, GraphQL, gRPC, or WebSocket APIs against the OWASP API Security Top 10 — object- and function-level authorization (BOLA/BFLA), excessive data exposure, mass assignment, unrestricted resource consumption, and GraphQL-specific abuse. For apps you own or are authorized to test.
File Upload and Ssrf
49mn-youssef/security-skills
Use when testing file-upload handling, server-side request forgery (SSRF), and insecure deserialization — upload bypasses (type/extension/content, polyglots, path traversal), SSRF to cloud metadata and internal services, and unsafe deserialization sinks. On apps you own or are authorized to test.
Authentication Testing
49mn-youssef/security-skills
Use when testing login, sessions, password reset, OAuth/OIDC/SAML/SSO, MFA, and JWTs for weaknesses that lead to account takeover — credential attacks, session fixation, reset-token poisoning, MFA bypass, and token forgery. On apps you own or are authorized to test.
Injection Testing
49mn-youssef/security-skills
Use when dynamically testing whether untrusted input reaches an interpreter — SQL/NoSQL injection (incl. blind/time-based), OS command injection, server-side template injection (SSTI), XXE, LDAP/XPath, and CRLF/header injection. Confirms on a running app what security-code-audit finds in source.
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.