Borrowing it
Nothing to install: this file belongs to vucinatim/air-jam. 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/vucinatim/air-jam/main/CLAUDE.mdgit clone --depth 1 https://github.com/vucinatim/air-jamWrote 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/vucinatim/air-jam/claude-md)<a href="https://agentmods.dev/instructions/vucinatim/air-jam/claude-md"><img src="https://agentmods.dev/badge/instructions/vucinatim/air-jam/claude-md/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/instructions/vucinatim/air-jam/claude-md"><img src="https://agentmods.dev/badge/instructions/vucinatim/air-jam/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00388 | $0.00388 |
| Opus 5 | $0.00194 | $0.00194 |
| Sonnet 5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
Grade A, and why
air-jam CLAUDE.md 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 8d 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.
What it actually says
Claude Workflow Notes
Use the same Air Jam development path as every other agent.
Local Launch
Start local development with:
pnpm run dev
Do not use raw vite for normal Air Jam work. It skips the local Air Jam server.
Do not create or prefer a separate preview-specific dev command. If local runtime state looks stale, use Air Jam status/log/reset tooling before debugging gameplay code:
pnpm run status
pnpm run reset:local
pnpm exec air-jam-server logs --view=signal
After editing host-only runtime refs, physics loops, or useHostActionListener side effects, hard refresh the host or run pnpm run reset:local if actions appear duplicated or rendered state no longer matches replicated state.
Preview Controllers
Use visible preview controllers for UI smoke proof:
- click buttons with real browser clicks
- drag controls with real browser drag/release gestures
- verify that the controller visually connects and can trigger at least one visible action
Do not synthesize pointer events into controller iframes from parent-page eval. That path is brittle around iframe boundaries, pointer capture, and React event timing.
Gameplay Proof
Use the game-owned agent contract for reliable gameplay assertions:
airjam.open_game_sessionairjam.read_game_sessionairjam.invoke_game_session_actionairjam.close_game_session
Use semantic actions for gameplay mechanics, physics outcomes, scoring, reset, and state assertions. Preview controllers are for visible UI smoke proof, not the primary automation lane.
Game Authoring Rule
Multiplayer games should be controllable from controllers. If a game has a start, ready, reset, or similar primary flow, expose it through controller UI and semantic agent actions. The host screen should not be the only place where play begins.
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.
- 8d ago First seen · 49 lines · 388 tokens per session scan A 4b5608f8333a
air-jam CLAUDE.md is an instructions file published in the GitHub repository vucinatim/air-jam (6 stars, last pushed today), licensed MIT. It adds 388 tokens to every session, about $0.0019 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.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.