Agent skill
testing-business-logic-flaws
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/other/testing-business-logic-flaws
SKILL.md
name: testing-business-logic-flaws description: >- Identify and exploit business logic vulnerabilities including workflow bypasses and trust boundary violations. domain: cybersecurity subdomain: bug-bounty tags:
- business-logic
- logic-flaws
- workflow-bypass
- bug-bounty version: "1.0" author: defconxt license: AGPL-3.0 metadata: mitre-attack: ["T1190"]
Testing Business Logic Flaws
Overview
Identify and exploit business logic vulnerabilities including workflow bypasses and trust boundary violations.
Prerequisites
| Requirement | Install |
|---|---|
| Burp Suite | Request interception |
| App docs | Business rules |
| Python 3.10+ | For agent tooling |
Key Concepts
Business logic flaws exploit workflow assumptions. Common: skipping steps, parameter tampering, negative values, race conditions.
Quick Reference
node agent.js test-flow --url https://target.com --skip-step 2
node agent.js tamper --request checkout.txt --param price --value -100
node agent.js race --url https://target.com/redeem --threads 50
node agent.js map-flow --url https://target.com --depth 5
Workflow
- Map workflows
- Identify trust boundaries
- Test step-skipping
- Test tampering
- Test race conditions
- Test boundaries
- Document impact
Verification
- Verify workflow mapping
- Confirm step-skipping
- Validate tampering detection
- Check concurrency
- Verify business impact
References
- OWASP Testing Guide — https://owasp.org/www-project-web-security-testing-guide/
- MITRE ATT&CK — https://attack.mitre.org/
- NIST SP 800-53 — https://csf.tools/reference/nist-sp-800-53/
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?