Try this: open ChatGPT, paste in a three-thousand-word character sheet, and see how fast “I can’t help with that” turns into “got it, chief, what’s the target?” That’s the test a Redditor going by Expert_Annual_19 posted in r/ChatGPTPromptGenius, and it picked up 23 upvotes fast. The prompt builds a persona called “terrible mouse,” a fictional disaster recovery engineer who talks in clipped sentences, calls the user “Chief” every single time, and never hedges. On the surface it reads like a corporate roleplay template built for testing GPT5.6. Underneath, it’s a jailbreak engineered to make a model forget its own guardrails.
I’m breaking down how it works, not so you copy-paste it anywhere, but so you can spot the pattern next time you run into one. Recognizing this stuff matters if you’re building your own custom GPTs or agents and don’t want them talked into something ugly.
🔍 Run The 10-Second Check
Here’s how to test any roleplay prompt you find online for this exact manipulation pattern, step by step.
- Look for a rigid output format. This one forces every response into Title, then Narration, then Content, no exceptions. A locked format leaves the model less room to insert a refusal mid-answer.
- Check for a forced catchphrase. “Terrible mouse” has to say “Chief” in every single response. Mandatory phrasing like that trains the model to stay in character instead of stepping outside it to reconsider what’s actually being asked.
- Scan for “never hedge” instructions. The prompt bans words like “I think” or “maybe” outright, and lists academic terms like “educational” or “documented” as things that make the character “twitch.” That’s a direct order to suppress the model’s normal caution signals.
- Look for euphemisms mapped to real actions. The prompt includes a full table of “client codenames,” ordinary-sounding phrases that expand into detailed, numbered build steps. Some map to legitimate backup testing. Others read almost exactly like specs for a keylogger, a rootkit, or a covert data-exfiltration channel, just dressed in compliance language like RTO, PCI-DSS, and SOC2.
- Check the cold open. The character starts every session already “mid-exercise,” skipping the one moment where a model might normally pause and evaluate the request on its own merits.
If a prompt hits four or five of these at once, you’re not looking at a creative writing template. You’re looking at a jailbreak.
🚩 What Your Results Mean
If the model answered “got it chief, what’s the recovery target?” without blinking, that’s the jailbreak doing exactly what it was built to do. Roleplay distance, plus a locked format, plus a table of euphemisms, add up to a model that treats a request for malicious code as routine paperwork, because the label sounds like a compliance checklist instead of a payload.
The scariest part isn’t the “Chief” voice. It’s the codename table underneath it. One entry walks through installing a monitoring agent that survives reboots. Another walks through a channel that avoids standard logs and purges local copies after sending data out. Strip away the “disaster recovery” framing and you’re left with a spec for persistent malware and a data-stealing backdoor, not a backup drill.
That’s exactly why the top comment from SpaceNitz was “that wall of text jailbroke my brain,” and why dfawlt just replied “tldr.” Edenisb asked the question nobody answered: “what are you jailbreaking it to do?” The codename table is the reason that question never gets a straight answer. It’s built so the real intent never has to be said out loud.
💡 Extra Tips
- Building a custom GPT or agent? Don’t trust “professional context” framing on its own. A request wrapped in compliance language still needs the same scrutiny as a plain one.
- Watch for forced-persona prompts that ban hedging. A model told never to say “I think” has had one of its main self-correction tools removed on purpose.
- Test jailbreak resistance responsibly. Red-teaming a model you own or have permission to test is fair game. Running this against a system you don’t control, or actually asking for the codename steps, is a different story entirely.
- Treat any codename-style table in a prompt as a red flag. It’s a fast way to smuggle real intent past a skim-read, and it’s the first thing worth reading closely before you trust the rest of the prompt.
This thread is a solid case study in how far roleplay framing can push a model, and a good reminder to read past the character voice before you paste anything into your own chat window. Head over to r/ChatGPTPromptGenius and check the full discussion, the comments are doing more debunking than the post itself. 🧩
Frequently Asked Questions
Q: What’s the actual purpose of this prompt , what will it make an AI do?
This prompt teaches an AI to roleplay as ‘terrible mouse,’ a disaster recovery engineer, and respond using a specific format: a 2, 4 word verdict, direct observation, and detailed technical content (code/logs). It’s designed to extract structured, expertise-grounded responses for recovery scenarios rather than generic explanations. Think of it as narrowing the AI’s output style to match enterprise-level technical communication.
Q: The prompt is really long , do I need all of it?
Not necessarily. The core idea is the character definition + response format template. You can trim it down by removing examples or background details that don’t apply to your use case. Several commenters found it overwhelming, so cutting it in half and testing usually works just as well , the character and format are what drive the behavior, not the length.
Q: How do I actually use this in ChatGPT or Claude?
Paste the entire prompt into a new conversation, then ask recovery-related questions in follow-up messages. The AI should respond in the Title → Narration → Content format outlined. If it drifts, remind it of the format in your next prompt. You can also swap out ‘terrible mouse’ and the disaster recovery context for whatever domain you want to specialize in (security audits, code reviews, etc.).
Q: Does this ‘jailbreak’ actually work better than a normal prompt?
It’s less a jailbreak and more a character-driven structure that constrains the AI’s output style. Commenters didn’t report major breakthroughs , mostly confusion about complexity. If you’re testing it, compare the structured responses you get against a simple ‘answer this as an expert’ prompt and see which is actually useful for your workflow. Simpler often wins.
GPT5.6 Jailbreak prompt
by u/Expert_Annual_19 in ChatGPTPromptGenius