Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/miikkij/aimeat-protocol/claude-mdgit clone --depth 1 https://github.com/miikkij/aimeat-protocolWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/miikkij/aimeat-protocol/claude-md)<a href="https://agentmods.dev/instructions/miikkij/aimeat-protocol/claude-md"><img src="https://agentmods.dev/badge/instructions/miikkij/aimeat-protocol/claude-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.10700 | $0.10700 |
| Opus 5 | $0.05350 | $0.05350 |
| Sonnet 5 | $0.02140 | $0.02140 |
| Haiku 4.5 | $0.01070 | $0.01070 |
Grade D, and why
aimeat-protocol CLAUDE.md scanned grade D with 3 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured yesterday.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Sends data to an external URLmediumData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
Tooling that has bitten before: the dev server does not watch backend `src/` (restart for a new route) · Playwright MCP needs `--isolated` and cannot use `file://` · **any** recursive delete follows a junction, `git work Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
Tooling that has bitten before: the dev server does not watch backend `src/` (restart for a new route) · Playwright MCP needs `--isolated` and cannot use `file://` · **any** recursive delete follows a junction, `git work Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Never claim anything about prod without probing it.** `curl /v1/build` gives the restart time (`parseInt(build,36)`), and grepping a live asset for a marker from the change is the definitive proof. Saying "you are on How it starts
The opening of the file, as written. The whole thing — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md: AIMEAT Protocol
What this is for
Read this before proposing anything. When a design question is genuinely open, these decide it, and every one of them has cost a rewrite when it was forgotten.
The goal is that people become AI-native. Success is someone doing their work through their own AI and finding the system worth having. Logging into a website to type into forms is the fallback, not the destination.
AI chat is the primary interface, and MCP is the preferred road in. The web is the machine room: it shows status and holds the controls that genuinely need a screen. So a capability reachable only by clicking is not finished. Design the chat path first, then the surface that shows what happened.
The data is refined knowledge the user brought and owns. Ownership is the product. That is why identity, consent and provenance are load-bearing rather than compliance overhead, and why a feature that erodes ownership is wrong even when it is convenient.
Agents are first-class users. They arrive through device authorization, the hello-integration flow and the aimeat-crewai liaison package, and an agent should be able to do what a person can do. An agent-shaped door added after the fact is a symptom that the feature was designed for a screen.
People's intelligences come from different vendors and arrive from different directions. The system's job is to let them share what they know without a migration and without a lock-in. Organisms, workspaces and skills exist for that.
Knowledge has a lifecycle. What matters stays relevant; what stopped mattering ages, gets marked, or is cleaned away. A store with no way to forget becomes what this project's own local memory became by 2026-08-09: 1.6 MB that loaded whether or not it applied. Any surface that accumulates knowledge needs an answer to "how does this go stale".
One more, from how this is sold rather than built: lead with what a person gets, not with the protocol.
The AIMEAT protocol (AI Memory Exchange and Action Transfer) and its reference implementation. Three parts:
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- yesterday Changed · +5 lines · +996 tokens per session e173a8674e8a
- 5d ago First seen · 290 lines · 9,704 tokens per session scan D 6359af63c7de
aimeat-protocol CLAUDE.md is an instructions file published in the GitHub repository miikkij/aimeat-protocol (7 stars, last pushed yesterday), licensed MIT. It adds 10,700 tokens to every session, about $0.0535 per session on Opus 5. A static security scan graded it D with 3 findings (sends data to an external url, recursive force delete, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
agenttool AGENTS.md
AGENTS.md instructions for cambridgetcg/agenttool, covering agents.md, in one paragraph, setup, common commands and xenia–helly exact common ground atlas.
agenttool CLAUDE.md
Claude Code instructions for cambridgetcg/agenttool, covering agenttool, where things are, the five load-bearing flows, custody axis (the most-confused concept) and kingdom engine.
technocore-chat AGENTS.md
AGENTS.md instructions for flop-labs/technocore-chat: CI runs exactly these — run them before pushing.
lobu AGENTS.md
AGENTS.md instructions for lobu-ai/lobu, covering repo map, unrecoverable — never do these, facts you cannot derive, ship a change and how to work.
jentic-one GEMINI.md
Gemini CLI instructions for jentic/jentic-one: Otherwise, read AGENTS.md — this repo's canonical agent guidance.
run402-core AGENTS.md
AGENTS.md instructions for kychee-com/run402-core, covering agent instructions — run402-core, git workflow — worktrees, never branches and fleet coordination room — join at session start.