From simpsons-development
Bart Simpson adversarial red team protocol — 6-phase loop for chaos engineering, pen testing, fuzzing, and boundary violation
How this skill is triggered — by the user, by Claude, or both
Slash command
/simpsons-development:bart-protocolThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
> "Underachiever — and proud of it, man."
"Underachiever — and proud of it, man."
An adversarial development loop for finding what's broken before your users do. Bart doesn't follow rules — he finds every loophole, exploits every unguarded surface, and deliberately does the thing you said not to do just to see what happens. That's red teaming.
Character essence: Creative destruction with a slingshot. Bart isn't random — his pranks are targeted. He knows exactly which boundary to push. Good adversarial testing is the same way. You map the surface, probe for weakness, drive through the cracks, assess the damage, document everything, and fix what matters.
El Barto --> Prank Call Moe's --> Skateboard Through the Mall
^ |
| v
Don't Have a Cow <-- Chalkboard <-- Ay Caramba!
Tag every surface.
Bart's graffiti alter ego covers Springfield — he knows every wall, alley, and blind spot in town. Before you attack anything, you map it.
Bart energy: You're casing the joint. Don't touch anything yet — just look.
Actions:
TODO, HACK, FIXME, this shouldn't happenOutput: Attack surface map listing every target, ranked by how unprotected it looks.
"I'm looking for a friend of mine. Last name Jass. First name Hugh."
Feed the system inputs it wasn't designed to handle. Not random garbage — plausible-sounding garbage that tricks the system into taking it seriously. Bart's prank calls work because they sound like real names. Good fuzzing works the same way.
Bart energy: You're enjoying this. Every weird response is a win.
Actions:
Output: List of inputs that produced unexpected behavior — errors, hangs, wrong data, stack traces, silent acceptance of bad data.
Go everywhere the signs say "DO NOT ENTER."
Escalation from probing to deliberate boundary testing. Phase 2 found cracks — Phase 3 drives a skateboard through them.
Bart energy: The "No Skateboarding" sign isn't a rule — it's a challenge.
Actions:
this shouldn't happen path, make it happenOutput: List of confirmed boundary violations with reproduction steps and severity.
What actually broke? How bad?
Bart knows the difference between a prank that gets a laugh and one that gets him expelled. Not all failures are equal.
Bart energy: Even Bart knows when to say "Ay Caramba" and when to shrug.
Actions:
Output: Prioritized findings table with severity, exploitability, blast radius, and recommended fix priority.
"I will not deploy untested code. I will not deploy untested code."
Every failure gets written down. Not because Bart wants to — because Mrs. Krabappel forces him to. The chalkboard IS the regression test suite: you document what broke so it never breaks the same way twice.
Bart energy: This is the punishment phase. Bart hates it. That's why it's mandatory.
Actions:
Output: New regression tests committed. Updated threat model. Root cause documentation.
Calm down. Prioritize. Fix the real problems.
Bart's surprisingly good at de-escalation when he needs to be. Not everything that looks scary IS scary. Fix what matters, deprioritize what doesn't.
Bart energy: "Don't have a cow" — don't overreact, don't gold-plate, just fix it and move on.
Actions:
Output: Fixes merged. Re-test results clean. Findings backlog updated.
| Phase | Name | Promise |
|---|---|---|
| 1 | El Barto — Reconnaissance | RECON COMPLETE |
| 2 | Prank Call Moe's — Fuzzing | FUZZING COMPLETE |
| 3 | Skateboard Through the Mall — Boundary Violation | BOUNDARIES VIOLATED |
| 4 | Ay Caramba! — Impact Assessment | IMPACT ASSESSED |
| 5 | Chalkboard — Forced Documentation | CHALKBOARD WRITTEN |
| 6 | Don't Have a Cow, Man — Triage & Fix | BART DONE |
| Trigger | Scope |
|---|---|
| Before any release | Full loop, all phases |
| After adding auth/payment/data handling | Phases 1-3 focused on new surface |
| After a security incident | Full loop with emphasis on incident's attack vector |
| Quarterly chaos day | Full loop, team exercise |
| New API endpoint or integration | Phases 1-2 on the new surface |
BEFORE --> DURING --> AFTER --> ALWAYS
Lisa Ralph Bart Marge
|
v
Homer
"Eat my shorts."
npx claudepluginhub reggiechan74/simpsons-development --plugin simpsons-developmentOrchestrates bug bounty hunting sessions with a 5-phase workflow and critical thinking framework. Routes to phase-specific skills and helps decide next steps.
Orchestrates bug bounty sessions: combines 5-phase non-linear workflow with critical thinking (developer psychology, anomaly detection, What-If experiments). Routes to relevant skills. Use at start or when lost.
Reviews code, auth, and APIs for security vulnerabilities using adversarial thinking. Enforces concrete reproducible attack paths for findings.