Model Context Protocol · Claude Code · Codex · Cursor
Teach it once.
Every agent knows.
Drop in screenshots and files. mozg turns them into a searchable brain your coding agents read over MCP — and tells you how much it still doesn't know.
What people put in one
The things you explain twice a week.
Design systems
Our components, not Tailwind's
Exact spacing, the states you actually ship, and the three rules everyone breaks.
Backend & APIs
The integration as it really runs
Your retries, your idempotency keys, the webhook order — not the vendor's happy path.
Game development
Engine conventions and math
How a mechanic is wired, what the pipeline expects, which numbers are load-bearing.
Product & process
What nobody wrote down
Naming, review rules, the deploy sequence — the folklore a new agent never gets.
What nobody else does
Every brain sits an exam.
You write what the brain is for. mozg turns that into control questions and runs them after every upload. So you get a number you can trust — and a list of exactly which material is missing, instead of guessing why your agent still gives bad answers.
Brain · Design system
32 checks · 4 categoriesOne brain, every agent
Claude learns it on Monday, Codex knows it on Tuesday. Built-in agent memory stays locked to one vendor; a brain does not.
Agents write back
An agent that works out a convention saves it. You approve it in a review queue, so the brain gets sharper instead of noisier.
Yours to take
Export any brain as CLAUDE.md, a Claude Skill or AGENTS.md. It keeps working if you stop paying us.
Start here
Four pages, then you're running.
Why this exists
What a brain is, and why agent memory built into one vendor isn't the same thing.
02Build a good brain
What to feed it, how to write a goal that becomes a real exam, and what a low score means.
03Connect your agent
Copy-paste setup for Claude Code, Codex, Cursor, Kimi, DeepSeek, GLM and Qwen.
04Or take one that exists
A catalogue of brains other people built, by field, free and paid.
In the catalogue now
all brains →Stake Engine
Answer any question about building and shipping a slot game on Stake Engine: the RGS wallet endpoints and how a round is served, how the maths model is built and simulated, how the frontend consumes its events, what approval requires, and the platform facts a game is launched with — currencies, dimensions, languages and URL structure.
Model Context Protocol
Answer any question about the Model Context Protocol as specified: the JSON-RPC messages and their exact shapes, the lifecycle from initialize to shutdown, tools, resources and prompts, transports, authorization, and what a client and a server each must do.
Stop explaining the same thing.
The free plan holds one brain, fifty sources and three hundred agent calls a month — enough to find out whether this works for you.