Build a meme-keyword programming language for AI agents

A Redditor had Claude Code write Memesis, an interpreted language for agents with meme keywords, a taint check that stops untrusted data reaching irreversible actions, and 34 tests.

Done withClaude Code· Nov 5, 2026

What they did

The poster, u/jvon5808, wanted a language for writing AI agents in which every keyword is an internet meme: pepe declares an agent, npc a function, thonk calls a model, apu asks a human, yolo marks an irreversible action and sus marks untrusted data. They came up with the concept and the keyword list, then handed the build to Claude Code. It wrote the lexer, parser, interpreter and a CLI with a check command for static analysis and an explain command that turns meme code into plain English. The poster described how untrusted data should be handled and Claude Code built the tracking and static checks for it. It also wrote the test suite and used Playwright to record the animated examples in the README.

How it went

The result is an open-source, MIT-licensed language on GitHub that runs locally, supports several agents and parallel tasks, and can call Claude or local models through Ollama. It ships with 34 tests. The poster calls the sus and yolo safety system the hardest part and says the project is still experimental. No time or cost is given. Commenters mostly found it funny.

Worth knowing

The joke has a real idea inside it: anything fetched from the web is tainted, and the runtime refuses to let it reach an irreversible action until code explicitly marks it as reviewed. One commenter pointed out that meme keywords make grepping and error messages harder to read, for people and models alike.

Try it

With Claude Code· 2 parts to fill in

Build a small interpreted language in [language of choice] for scripting AI agents, with its own file extension and these keywords: [my keyword list mapped to meanings such as agent, function, model call, ask a human, try/catch]. Write the lexer, parser, interpreter and a CLI with a run command, a static check command and an explain command that prints a script in plain English. Track untrusted data: anything fetched from the network is tainted and must not reach an action marked irreversible unless the script explicitly marks it reviewed, enforced both statically and at runtime. Write tests for each feature and stop when they all pass, then show me three example scripts before writing any docs.

Square brackets are the parts to fill in. The prompt is ours; the story is theirs.

Where they said it

Related