Menu
Run chaos security engineering tests — AI agent attempts to hack the Sprint output and reports findings to the team
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Validate Java and TypeScript code against banking naming conventions, style rules, quality standards, and secure coding practices
Perform OWASP Top 10 security assessments, vulnerability scanning, and PCI-DSS compliance checks
Design test strategies including security testing, write test plans, and identify test scenarios for banking features with DevSecOps integration
Perform STRIDE threat modeling during Sprint Planning for new features and APIs
Run UX review checklist for banking user flows, validate WCAG accessibility compliance, assess security UX patterns, and review customer interface design
Design, review, and validate API contracts and OpenAPI specifications for banking services
Based on SOC occupation classification
| name | chaos-security-testing |
| description | Run chaos security engineering tests — AI agent attempts to hack the Sprint output and reports findings to the team |
Invoke during or after Sprint development to proactively test the Sprint's output for security weaknesses. The AI agent acts as a "friendly hacker" trying to break the system.
# Chaos Security Test Report — Sprint [N]
## Tests Executed: [X]
## Vulnerabilities Found: [Y]
| # | Test | Category | Result | Severity | Details |
|---|------|----------|--------|----------|---------|
| 1 | IDOR on /accounts/{id} | AuthZ | FAIL | Critical | Can access other users' accounts |
| 2 | SQL injection on /search | Input | PASS | - | Parameterized queries working |
| 3 | Expired JWT access | AuthN | PASS | - | Returns 401 correctly |
## Recommended Sprint Backlog Items
- [ ] BANK-SEC-XXX: Fix IDOR on account endpoints (P0)