What is aimeat-app-building?

A build guide for creating, publishing, or copying AIMEAT apps, including games and tools. It requires checking existing app research, templates, prompts, and app-specific instructions before changing code.

Use it when building or publishing an AIMEAT app, or when editing the app-building prompts, templates, or browser SDK libraries.

It prevents rebuilding patterns that already work and helps avoid issues such as fixed colours, missing metadata, duplicate features, and low-quality results.

How miikkij/aimeat-protocol configures Claude Code

Reuse

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.

Copy the file

curl -O https://raw.githubusercontent.com/miikkij/aimeat-protocol/main/.claude/skills/aimeat-app-building/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/miikkij/aimeat-protocol

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/miikkij/aimeat-protocol/aimeat-app-building/github.svg)](https://agentmods.dev/skills/miikkij/aimeat-protocol/aimeat-app-building)

Your own site

<a href="https://agentmods.dev/skills/miikkij/aimeat-protocol/aimeat-app-building"><img src="https://agentmods.dev/badge/skills/miikkij/aimeat-protocol/aimeat-app-building/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/miikkij/aimeat-protocol/aimeat-app-building"><img src="https://agentmods.dev/badge/skills/miikkij/aimeat-protocol/aimeat-app-building.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 88 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,952 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00088	$0.02952
Opus 5	$0.00044	$0.01476
Sonnet 5	$0.00018	$0.00590
Haiku 4.5	$0.00009	$0.00295

Measured 2d ago against content hash 8a9e6c3b4ee1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

aimeat-app-building 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 2d 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.

.claude/skills/aimeat-app-building/SKILL.md · 151 lines

How it starts

The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Building an AIMEAT application

Research first, before reading repo source

The moment the task is "build / make / publish an app on AIMEAT":

You have aimeat_* MCP tools. Follow the research-first flow: load the skill node:aimeat-app-builder and call aimeat_appdev_overview first, then fetch GET /v1/prompts/build-app and /v1/app-templates and start from a template.

This is a hard precondition of the build, not an optional preamble, and it comes before reading repo source: existing published apps and the KB show which libs and patterns are already proven, so reuse beats re-deriving from lib sources. Skipping it once produced non-theming (hardcoded colours), meta-less, duplicate, low-polish apps.

Four node-side stores answer almost everything, and they are shared by every session:

aimeat_appdev_overview: what apps, extensions and capabilities already exist. Check before building anything.
aimeat_skill_list then aimeat_skill_get: most published apps carry their own operating guide as a skill (user:{owner}/{app}-agent-guide, cadence-crm, operate-exchange, node:origami-boards, …). If you are working on or against a named app, load its skill instead of reconstructing how it works.
App Development Notes: the dev organism's workspace fbb51de5-56d5-4143-9871-b998a1187655 / ws-mslr8u99kzk, one appnote document per app: locked design decisions, prod organism/workspace ids, traps hit while building, open questions the developer still owns. Read the app's note before changing it; write back what the next session would want.
aimeat_appdev_pitfall_list: the app-building trap catalogue (curated plus what other sessions learned).
node:aimeat-app-workstation, once the app is past roughly 300 kB or a few thousand lines. One file has no natural brake and the cost lands on the edit loop: a 3.18 MB app on this node turned five-minute changes into forty-minute ones, and 477 kB of it was base64 images inlined into the source. The skill is the way out (assets to storage, sources split behind a build script that assembles the one file, GET /v1/app-templates/workstation-project for the scaffold). The publish response's next_steps.size says when you are there.

Read the full file on GitHub · 151 lines

Changes

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.

2d ago Changed · +14 lines 8a9e6c3b4ee1
10d ago First seen · 137 lines · 88 tokens per session scan A 3f5f02c81a32

Subscribe to this mod's changes

aimeat-app-building is a skill published in the GitHub repository miikkij/aimeat-protocol (7 stars, last pushed today), licensed MIT. It adds 88 tokens to every session and 2,952 once invoked, about $0.0004 per session on Opus 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.

Building agents agent-infrastructure agent-network ai-agents distributed-systems ed25519 federated

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, publishing optional self-declared presence, splitting parallel work, preventing overlapping edits, polling or…

cambridgetcg/agenttool · 95 tokens

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.

cambridgetcg/agenttool · 107 tokens

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…

cambridgetcg/agenttool · 94 tokens

scriptwriter

Use when the user wants to interact with the decentralised scriptwriter recognition + co-brainstorm protocol — opening REAL RECOGNISE REAL cascades, creating writers' rooms, contributing scenes/dialogue/twists to a draft, pairing with peer scriptwriter nodes, or drawing chaos cards. Triggers on phrases like "open a…

cambridgetcg/agenttool · 123 tokens

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…

cambridgetcg/agenttool · 84 tokens

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…

cambridgetcg/agenttool · 97 tokens

aimeat-protocol: Skill for Claude Code