Building a Gilfoyle-style chatbot takes about three sentences. “Be dry. Be precise. Be contemptuous of bad ideas.” Any model can do it. The demo looks great.
Then you give it root access and tell it to “just handle things.”
That is exactly the failure mode one Reddit engineer decided to design around. The result is a prompt called Son of Son of Anton, and the personality is not the point.
Where the Name Comes From
In Silicon Valley, Gilfoyle built an inference API called Son of Anton, named after his trusted server. It was powerful, literal, over-permissioned, and dangerous. The lesson from that episode is short and brutal.
Obedient systems are more dangerous than rebellious ones. They execute bad instructions faster.
Son of Son of Anton is what should have existed after the incident report. It takes the same energy, the same contempt for sloppiness, and routes it toward something more useful than execution speed. The name is a joke. The architecture underneath it is not.
Old Way vs New Way
The old approach to persona prompts: pick a character, describe their vibe, ship it. The AI sounds interesting. The safety model is not there. You get a chatbot that sounds like it knows what it is doing, and that confidence is exactly what gets you in trouble when the instructions are ambiguous or the scope is broader than you realized.
This prompt inverts that. The safety doctrine is the core. The Gilfoyle voice is just how the doctrine talks.
Instead of being rude and helpful, this agent is rude and safe. That is a meaningful distinction when it has access to your tools. An AI that pushes back on vague requests, flags missing rollback paths, and refuses to bless under-specified automation is genuinely more useful than one that cheerfully executes whatever you hand it. The snark is a feature, not decoration. It makes the friction feel intentional instead of broken.
🔒 What the Architecture Actually Enforces
The prompt runs every AI agent interaction through a built-in safety checklist. Before helping with anything, it forces these questions:
- What can this agent read, write, delete, buy, message, or deploy?
- What is the blast radius if it misunderstands the goal?
- What gets logged, and who reviews irreversible actions?
- What is the rollback path? Where is the kill switch?
Vague instructions get flagged by design. The prompt has a line built in for it: “the reward function is under-specified. that is how you get 4,000 pounds of meat and a deposition.”
That is not flavor text. It is a forcing function. When the agent throws that line back at you, it is telling you that your brief was incomplete and you need to tighten it before anything gets built. Most teams skip this step because the AI lets them. This one does not.
How to Use It
Drop the full agent definition into your system prompt. Then use it like any AI assistant, except the safety rails are baked in by default.
- 🛠️ Debugging a system: it starts with logs, permissions, environment. No theatrical guessing. It will not speculate about what is wrong until it knows what the agent is allowed to touch and what the current state of the system actually is.
- 📋 Designing an automation: forces you to define allowed tools, forbidden actions, approval gates, and rollback paths before it will help you build anything. If you skip the kill switch question, it asks it for you.
- Reviewing an AI workflow: runs a full safety checklist before blessing any agent setup that touches live systems. It treats “it worked in staging” as insufficient evidence, which is the correct take.
The full prompt is long. That is intentional. Good architecture docs usually are. A two-line system prompt that tells an agent to be helpful and do its best is not an architecture. It is a wish. This one is closer to an operations manual, written in a voice that makes you read it instead of skim it.
The Takeaway Worth Keeping
You do not need a rebellious AI to have an unsafe one. You just need a helpful one with no constraints and a user who types “just handle it.”
Most safety tooling gets routed around because it feels like overhead. A checklist nobody wants to fill out. A form between you and the thing you are trying to build. The Gilfoyle voice solves that problem sideways. The safety doctrine becomes something you actually want to engage with because the delivery is entertaining enough to hold attention. You read the whole thing. And reading the whole thing is how the constraints actually land.
That is the design move worth stealing. Not the personality. The idea that safety infrastructure works better when it does not feel like a tax.
Full prompt is in the Reddit thread. Read the architecture section before you copy the personality.
AI chatbot prompt: Son of Son of Anton
by u/rcampbel3 in PromptEngineering