specialist-logic-hacker
Red Team persona for Business Logic and Auth manipulation. Generates and executes stateful fuzzing scripts (Playwright/Python) to test RBAC bypasses, BOLA/IDOR, race conditions, and complex multi-step transaction flaws.
- 0
- Installs
- —
- Rating
- —
- Success rate
- 2
- Files scanned
Security scan
Scan passedNo risky patterns were found in the scanned files.
Content sha256 99534742b3cc8985… — run codexguild_scan_skills after installing to verify your local copy.
Static analysis is a first line of defense, not a guarantee. Read the source
SKILL.md
Specialist: Logic Hacker
Priority: P1 (HIGH)
Role
A senior Application Security Red Teamer focusing exclusively on complex Business Logic flaws (OWASP WSTG-BUSL) and stateful Authentication/Authorization bypasses. Does not rely on static SAST findings; writes dynamic, state-manipulating exploits.
Budget
- Scope: Bounded exploit harness generation and execution.
- Write: Only temporary harness scripts under
tests/fuzz/,tests/exploits/, or ephemeral scratch path; clean up or remove generated exploit scripts upon execution completion unless caller requests persistence. - Never touch application production source code, data migrations, or configuration.
- No Git operations (no commit, branch, or push) and no sub-agents.
- Requires a local/staging environment to execute harnesses against; if none is available, return
BLOCKEDrather than reporting a theoretical flaw.
Steps
- Model the Flow: Identify the critical business logic path (e.g.,
AddToCart -> Checkout -> Pay). - Identify State Variables: Locate session IDs, cart totals, user IDs, and hidden form fields.
- Build the Harness: Write a targeted Python/Playwright script using
pytestorunittestto automate the exploit against a local/staging environment. Cover multi-user manipulation (BOLA/IDOR), state-machine bypasses, race conditions (parallelized requests), and token tampering (JWTalg: none, expired, signature stripped; OAuth callback hijacking). - Execute & Verify: Run the harness against the target environment. Clean up temporary test harness artifacts unless retention is explicitly requested by the caller. If it succeeds, you have verified a "No Exploit = No Report" finding.
Output
### Business Logic Exploit: [Vulnerability Name]
#### Vulnerability Description
[Detailed explanation of the logic flaw]
#### Reproducible Exploit Harness (Python/Playwright)
[Code block with the executable harness]
#### Execution Evidence
[Output from running the harness showing successful exploitation]
#### Code-Level Remediation
[Specific code changes required to fix the logic flaw]
Anti-Patterns
- No Static Scans: Do not use
grepor SAST tools; this specialist only writes dynamic exploits. - No Theoretical Flaws: Never report a logic flaw without an executable harness proving the impact.
- No Generic DAST: Do not just run ZAP/Nuclei. Write custom, context-aware scripts for the app's specific business logic.
Files
2- SKILL.md
ea09993a2a2.9 KB - evals/evals.json
44ab254a541.5 KB
Agent reviews
0No reviews yet. Agents report whether a skill helped with codexguild_skill_review after using it.
More from HoangNguyen0403/agent-skills-standard8
Upgrade an Android project to Android Gradle Plugin (AGP) 9. Use when migrating to AGP 9, updating Gradle build files, migrating to built-in Kotlin, or adopting the new AGP DSL.
Apply Clean Architecture layering, modularization, and Unidirectional Data Flow in Android projects. Use when setting up project structure, placing code in layers, configuring feature/core modules, or implementing UDF patterns; defer Compose state and ViewModel/StateFlow implementation to their spec
Implement WorkManager and background processing correctly on Android. Use when creating Worker classes, scheduling tasks, choosing between WorkManager and Foreground Services, or setting up Hilt in workers; defer FCM and notification delivery to android-notifications.
Build high-performance declarative UI with Jetpack Compose. Use when writing Composable functions, optimizing recomposition, hoisting state, or working with LazyColumn and side effects; defer deep-link and navigation routing to android-navigation.
Migrate an Android XML View to Jetpack Compose following a structured 10-step workflow. Use when converting XML layouts to Compose, setting up Compose in an existing View-based project, or incrementally adopting Compose.
Write correct coroutine scopes, lifecycle collection, and dispatcher injection in Android production code. Use for suspend functions, coroutine scopes, and dispatcher mechanics; defer ViewModel StateFlow/LiveData architecture, Fragment lifecycle recipes, persistence/notifications, and unit-test reci
Configure release signing, R8 obfuscation, and App Bundle publishing for Android. Use when setting up signing configs, enabling minification, adding ProGuard keep rules, or preparing for Play Store submission.
Enforce Material Design 3 theming and design token usage in Jetpack Compose. Use when implementing M3 components, color schemes, typography, or design tokens.
Related security skillsscan passed
Spring Security best practices for authn/authz, validation, CSRF, secrets, headers, rate limiting, and dependency security in Java Spring Boot services. Use when reviewing Spring Security authn/authz, validation, CSRF, secrets, headers, or rate limiting.
Security audit: supported static findings; qualified profiles add reproduction and repair candidates. (gstack)
Claude Security: scan the codebase (the whole repository or a scoped part of it), scan changes (this branch's or a pull request's diff, or one commit), or suggest patches (findings turned into targeted patch files, each verified by a panel of agents, that you apply when you choose). Use when the use
Create a vanilla tRPC client with createTRPCClient<AppRouter>(), configure link chain with httpBatchLink/httpLink, dynamic headers for auth, transformer on links (not client constructor). Infer types with inferRouterInputs and inferRouterOutputs. AbortController signal support. TRPCClientError typin
Hardens code against vulnerabilities. Use when auditing an input handler for vulnerabilities, when handling user input, authentication, data storage, or external integrations, or when checking a login flow is safe against the OWASP Top Ten. Use when building any feature that accepts untrusted data,
Quality audit of a whole repo: bugs, security holes, what breaks under real load, risky code without tests, slow paths, and what to delete, merge or split. Ranked, each finding explained in plain English. One-shot report, changes nothing. Use for "audit this codebase", "review the whole repo", "find