Hack Merlin, the Free Prompt Injection Game, Just Lost Its Token Sponsor and Needs a New One

Fresh drop on r/PromptEngineering, and this one is a request for help rather than a launch. For a few years, u/galcia has hosted hackmerlin.io, a hobby project where you try to beat an AI with prompt injection. The setup is simple and sticky. A wizard named Merlin guards a secret password, and you have to talk, trick, or trap it into giving the password up. Each level makes the wizard harder to fool, so what starts as a ten-minute curiosity turns into a real lesson in how language models follow instructions. Now the project has lost its token sponsor. Microsoft Poland covered it for years, and the author thanked them openly in the post.

The twist is what the project actually runs on. It’s not servers or a big team. It’s tokens. Every time someone pokes at the wizard and tries to talk it out of its secrets, a model call gets paid for. A game like this can get a lot of attempts per player, because people retry, rephrase, and share their tricks with friends. When the sponsor stops, the game stops, unless someone new steps in. A static website can sit online for pennies. A game built on live model calls cannot, and that gap is exactly why a sponsor matters so much here.

The author says they were planning a new update, but now they don’t know the project’s future. That’s the part that stuck with me. A game that teaches people how prompt injection works is exactly the kind of thing the AI community should want to stay online. Most people learn about this attack from a slide or a blog post and never feel it. Hack Merlin lets you feel it, and that is how the lesson sticks. Security awareness works best when people get to try the attack in a safe sandbox where nothing real is at risk.

The transparency is also worth noting. The project is open source on GitHub (bgalek/hackmerlin.io), and the traffic stats are public on Plausible. Anyone considering sponsoring can look at real numbers before they commit. That’s rare for a hobby project. Most sponsorship pitches ask you to trust a vague claim about reach. Here you can check the audience size, see where visitors come from, and read the code to understand how requests are made. For a company evaluating a small, low-risk sponsorship, that kind of openness removes most of the friction.

Here’s the mini-workflow if you want to do something about it:

  1. 🎯 Play it first. Go to hackmerlin.io and try to break the wizard. You’ll know in a few minutes why people email the author about it. Pay attention to which of your tricks work on early levels and which fail later, because that progression is the real lesson.
  2. 📊 Check the numbers. Open the public Plausible page for hackmerlin.io and see the traffic yourself. Look at the trend over time, the top referrers, and the countries. If you plan to pitch a sponsorship internally, screenshots of this page are the strongest evidence you can bring.
  3. ⭐ Star the repo. The author says that if you can’t sponsor, a GitHub star still helps. It takes ten seconds. A visible star count also makes the project look healthier to any potential sponsor who lands on the page.
  4. 🤝 Pitch your company. If you work somewhere with an AI budget or credits, a token sponsorship for a well-known open source prompt injection game is cheap goodwill with a technical audience. Keep the pitch short: the audience, the cost, and what your brand gets in return.

Pro tips

  • If you run an AI product, this is a low-cost way to get your name in front of people who care about model security. Those people are often the engineers and security leads who influence which tools their teams adopt.
  • If you’re a founder or work in developer relations, send the link to whoever owns your API spend. Sponsoring tokens is easier to approve than sponsoring cash, because credits you already hold cost you very little to give away. Ask the author what monthly volume the game needs so you can quote a real number.
  • Use the game as a warm-up exercise for your team. Prompt injection is much easier to understand once you’ve tried it yourself. Run it as a ten-minute challenge in a team meeting, ask everyone to share the prompt that got furthest, and then talk about how you would defend your own product against the same tricks.
  • If you can’t sponsor but know someone who can, a short, friendly message with the link to the Reddit post is often the most useful thing you can do today.

Call to action: Play a round, star the repo, and if your team can sponsor tokens, reach out to the author through the post on r/PromptEngineering. Let’s keep Merlin alive. 🧙

hackmerlin.io – looking for support
by u/galcia in PromptEngineering

Scroll to Top