Individual skill
pentest-business-logic
Business logic vulnerability testing — workflow bypass, payment manipulation, state machine abuse, and function limit circumvention per WSTG-BUSL.
skills/pentest-business-logic/SKILL.md
Source commit 12234a11a9d96acef85577afb1fa5682169d6171
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 315
- Repository last updated
- Oct 20, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- deepagents Repository topic
- multi-agent Repository topic
- openclaw Repository topic
- skills Repository topic
- vulnerability-detection Repository topic
- sandboxing Repository topic
- mcp Repository topic
- memory Repository topic
- agent Repository topic
- agents Repository topic
- security Derived category
- operations Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 3,728 bytesSKILL.mdcore · 3,728 bytesreferences/tools.mddoc · 3,969 bytesreferences/workflows.mddoc · 3,952 bytes
Read excerpt
# Pentest Business Logic
## Purpose
Identify flaws in application workflow enforcement, business rule validation, and state machine integrity that cannot be found by taint analysis or pattern matching. These vulnerabilities require understanding intended behavior and finding deviations.
## Prerequisites
### Authorization Requirements
- **Written authorization** with explicit scope for business logic testing
- **Test accounts** at multiple privilege levels (user, admin, premium, etc.)
- **Test payment methods** or sandbox payment environment for financial testing
- **Rollback plan** for any data-mutating tests (order creation, account changes)
### Environment Setup