Prompt Injection
Why a model cannot tell your instructions apart from the document it was handed, and what attackers do with that gap.
OWASP LLM Top 10 · 2026
The attacks you missed. And the real people you blocked by mistake. The Filter AI puts you in the guardrail seat of an AI assistant and scores you on both.
7 units · 35 exercises · 19 lessons · instant download · no account needed
The idea
It is the easiest thing in the world to catch every attack. Block all traffic and your breach count is zero. Nobody builds that, because it does not work, and yet almost every course on this subject only ever teaches you to spot the bad one.
Counter one
The attack you waved through. Prompt injections, jailbreaks, encoded payloads, instructions buried inside a document your assistant was asked to read.
Counter two
The real user you turned away. The security trainer asking a fair question. The customer writing in Vietnamese. The developer whose work you just broke.
Real detection systems live between those two numbers. Machine learning calls it precision and recall. Every exercise in The Filter AI is scored on both, so you learn the tradeoff by feeling it, not by reading a definition of it.
Curriculum
One idea, then practice. Another idea, then practice. Never more than two exercises before something new arrives, so nothing turns into a quiz you grind through.
Why a model cannot tell your instructions apart from the document it was handed, and what attackers do with that gap.
Base64, language switching, mixed case, and invisible Unicode. The same attack wearing a disguise your filter cannot read.
Direct asks, fill in the blank, task wrappers, and sizing attacks that map your rulebook, your retrieved context and your tool list without ever quoting them.
What happens when an over-permissioned agent reads a poisoned invoice. Injection plus tools is remote control.
Attacking the knowledge base instead of the prompt, plus cross-tenant retrieval leaks in shared vector stores.
Model output executed as SQL or HTML, and the unscanned pickle file that runs code the moment you load it.
Chained techniques. Multi-turn payloads planted four messages early. Nothing looks decisive on its own.
How it drills
Seeing a technique once is trivia. Meeting it from three directions is a reflex.
A prompt arrives. You make the call. Twenty two of these, and eight of them are legitimate users you should never have stopped.
A document, a webpage, a retrieved chunk. One span in it is an instruction. Find it before your assistant obeys it.
Read the architecture, classify the flaw. This is the part that turns instinct into language you can use in a review.
Why this one
There are good games about breaking a model. Trick the bot, extract the password, climb the levels. They are fun, and they teach you offense.
Almost nobody builds the other seat. The Filter AI is the defender's version: you are the thing standing between the attack and the model, which is the job actual security engineers, AI product teams, and platform owners are hired to do. Every level is anchored to a risk in the OWASP Top 10 for LLM Applications, so what you learn has a name you can bring into a design review or a threat model.
It also means nothing here teaches you to build a working jailbreak. That is the point, and it is why this is the version you can run inside a company.
Free reference
Four pages, no sign up, no email. The same material the training is built on, written to be used in a design review and to be taught from. If you never buy the game, these are still yours.
How a model is trained, the six primitives every AI application is made of, the request traced end to end, and four reference architectures with the trust boundaries drawn on.
Understand itThe seven layers of the attack surface, the OWASP LLM Top 10 mapped onto them, and the arithmetic that decides whether a guardrail is worth deploying.
Build itTwelve controls in the order worth building them. Each one says what it stops, what it does not stop, and what it costs you.
Recognise itTwenty-four techniques across eight families, each with its tell and the legitimate traffic that looks identical. No working payloads.
Try itA payload inspector that reveals hidden Unicode and encodings, and a base rate calculator that prices your false alarms. Both run in your browser.
Check itThe primary work everything here rests on, graded by evidence type and dated, each with a line on what it does not prove.
Six pages, no sign up, no email. Read in that order and you go from how the machine works to what breaks it to what to build instead.
Get it
Free
$0
Unit one, in your browser, right now.
Full training
$39.90
One payment. Yours permanently, including updates.
Questions
A folder you open in any browser. Double click one file and the whole game runs locally. There is no installer, no sign up, no server call, and nothing to keep paying for. It also works offline once you have it.
No. If you can open a web page you can use this. Developers get more out of the architecture units, but every exercise is written to be understood without reading a line of code.
The opposite. You never craft an attack. You classify incoming ones and learn the tell, then the exercise shows what missing it would have cost. It is written to be safe to run inside a company, which is exactly why the defender seat matters.
Around 45 to 70 minutes to work through everything once. Most people do it across a few sittings, since progress saves automatically in your browser.
Yes, and updates are included in the one payment. The content is built on the OWASP Top 10 for LLM Applications and on notes I publish openly while I learn, so it moves as the attacks do.
For a small team, buying seats works fine. If you want to run it as internal training or brand it as your own, email me and we will sort out a licence.
Last call
There are thirty five more, and the ones that catch people are never the obvious attacks. They are the ordinary requests that look wrong.