Borrowing it
Nothing to install: this file belongs to miikkij/aimeat-protocol. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/miikkij/aimeat-protocol/main/.claude/skills/aimeat-organism-records/SKILL.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/skills/miikkij/aimeat-protocol/aimeat-organism-records)<a href="https://agentmods.dev/skills/miikkij/aimeat-protocol/aimeat-organism-records"><img src="https://agentmods.dev/badge/skills/miikkij/aimeat-protocol/aimeat-organism-records/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/miikkij/aimeat-protocol/aimeat-organism-records"><img src="https://agentmods.dev/badge/skills/miikkij/aimeat-protocol/aimeat-organism-records.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00104 | $0.01330 |
| Opus 5.5 | $0.00042 | $0.00532 |
| Sonnet 5.5 | $0.00021 | $0.00266 |
| Haiku 4.5 | $0.00010 | $0.00133 |
Grade A, and why
aimeat-organism-records scanned grade A with 0 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 1mo ago.
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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Organism records, roadmaps and ODPS listings
Applies only when an aimeat_* MCP server is connected. If none is, skip silently.
Where new design work is authored
New design specs, plans and roadmap items are records in the relevant AIMEAT organism on aimeat.io, not files in repo docs/. Deliberate dogfooding: our own knowledge work runs on our own product, and the data stays in the service we own.
Route to the organism where that product's roadmap lives: each MACHINE ROOM app to its own organism/FABRIC; the AIMEAT platform itself (including app-catalog) to the FABRIC roadmap hub.
Canonical in the repo, unchanged: openapi.yaml, the RFC sections and coding-guideline references under docs/, CLAUDE.md, docs/known_gaps.md.
Publishing is a gate. Draft freely; publish only on the developer's explicit go-ahead in this session. Never auto-publish.
Dev organism session rituals
Starting, claiming and handing off a session is not here. That ritual is skill aimeat-dev-session on the node (aimeat_skill_get), and it runs in organism AIMEAT CODING CENTRAL (da438a5f-609b-41e5-ad9f-8dd2cc76cbe1) through the Lifecycle Central tools: the board, claims, incidents, decisions, handoffs and the wish bucket (CLAUDE.md, "Working beside other sessions"). This section is about the DEV organism, where designs and build notes live.
Organism id fbb51de5-56d5-4143-9871-b998a1187655, reached with the node's MCP tools (mcp__claude_ai_AIMEAT__aimeat_workspace_*; the separate appdev connector this section used to name is gone). The repo stays source of truth for code and the protocol contract.
Workspaces: Development ws-mq664uyfz21, Handbook ws-mq6653ry24h, Protocol ws-mq665ahqc6b, Platform Development Notes ws-mslunjvcgxj, App Development Notes ws-mslr8u99kzk.
- Before design work: read the
contextdocmain-contextin Development and the last fewdecisions. Do not ingest the whole organism. - Planning a task: read just-in-time. The area's Handbook page(s), open
feature/bugrecords, relevantdecision/invariant. - Finishing significant work: update the
feature/bug; log adecisionorknown-gap(both gated on human approval); update the Handbook page and the sub-context doc's current-state. - Milestones: a sub-context draft is the live current-state and can be edited freely. A publish is a milestone and needs the developer's explicit go-ahead.
- Sync:
docs/known_gaps.mdand the roadmap are kept in step by hand. No command does it; thepnpm organism:syncthis line used to name was never written.
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.
- 1mo ago Changed · +2 lines 54f0fe860cb0
- 2mo ago First seen · 66 lines · 104 tokens per session scan A da310b13e67c
aimeat-organism-records is a skill published in the GitHub repository miikkij/aimeat-protocol (10 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 1,330 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
coordinate-agent-work
Coordinate independent coding or research agents across host sessions and linked Git worktrees through AgentTool Collab's local journal. Use when starting or resuming credential-bound coordination, splitting parallel work, claiming before overlapping edits, polling or acknowledging events, attaching evidence…
capability-conductor
A guide for finding and combining existing agent skills for one task while keeping track of where each skill came from and what limits it has.
nen-math-card
Frame a mathematical challenge as a bounded proof, model, or measurement inquiry and decide whether it can construct, repair, choose, or clarify anything. Use when a user asks whether a math problem is useful, wants to turn a competition or puzzle into reusable understanding, needs to separate formal proof from world…
nen-common-ground
Model several explicitly stated decision boundaries as convex feasible regions and return either shared room, a small conflict witness, or an honest refusal of the model. Use when the user invokes Helly, common-ground geometry, 共域, local-to-global agreement, constraint reconciliation, or a KINGDOM challenge about…
scriptwriter-room
Focused on writers' room operations — creating rooms with a seed prompt, contributing signed scenes/dialogue/stage-directions/twists/chaos-cards/notes, subscribing to the SSE live stream, polling for new contributions. Use when the user wants to actually draft something with peers, draw a chaos card to seed a scene…
scriptwriter-rrr
Focused on the REAL RECOGNISE REAL cascade flow specifically — opening cascades with a peer, escalating depth, verifying chains, surfacing wall refusals with their meaning. Use when the user explicitly references RRR depth, cascade verification, alternation walls, or the "I know you know I know" mutual-recognition…