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/AGENTS.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/agents-md)<a href="https://agentmods.dev/instructions/vucinatim/air-jam/agents-md"><img src="https://agentmods.dev/badge/instructions/vucinatim/air-jam/agents-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/agents-md"><img src="https://agentmods.dev/badge/instructions/vucinatim/air-jam/agents-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.02228 | $0.02228 |
| Opus 5.5 | $0.00891 | $0.00891 |
| Sonnet 5.5 | $0.00446 | $0.00446 |
| Haiku 4.5 | $0.00223 | $0.00223 |
Grade A, and why
air-jam AGENTS.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 13d 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 — 225 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Contract
This repository owns Air Jam's public framework, standalone server, creator tools and reference games. Studio, Arcade, accounts, hosted policy, databases and production operations belong to the private product repository. Develop one framework; the product consumes its supported package exports.
Source separation is under review and unfinished. Do not merge the ownership removal while Railway automatically deploys from the old public product paths. The private product's separation plan owns the guarded source handover; green framework checks do not establish private deployment readiness.
Mission
Build and maintain a clean, minimal, and extensible codebase that can scale without unnecessary complexity.
Ultimate Vision
Air Jam is not only a multiplayer game framework.
The long-term goal is for it to become an AI-native game creation and evaluation harness where a single prompt can drive the full lifecycle of building, testing, polishing, publishing, and iterating on a game.
The intended end state is:
- a user can ask for a game at a very high level, such as "make a mario kart clone"
- Air Jam's development harness can orchestrate multiple specialized agents in parallel
- different agents can own gameplay logic, assets, audio, music, UI, polish, balancing, testing, and release preparation
- agents can run the game directly, inspect logs, inspect visuals, read authoritative runtime state, and control players without relying only on browser automation
- the framework exposes clean machine-usable contracts for controller actions, state inspection, runtime events, visual feedback, and evaluation loops
- the same contracts work for both human development and agent-driven development
- the system keeps iterating until the game reaches a high level of finish and polish rather than stopping at a rough prototype
This vision has architectural consequences now:
- runtime, transport, controller input, replicated state, signals, logs, and preview surfaces must stay explicit and machine-readable
- behavior should be accessible through strong contracts rather than hidden in UI-only flows
- local preview, hosted preview, runtime authority, analytics, and publish flows should converge on one coherent operating model
- agent control surfaces should be treated as first-class future product requirements, not afterthought tooling
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.
- 13d ago Changed · -36 lines · -281 tokens per session 9fc4ad88e5b0
- 1mo ago Changed · +22 lines · +260 tokens per session d6da24275f1e
- 1mo ago First seen · 239 lines · 2,249 tokens per session scan A 9d053544fa12
air-jam AGENTS.md is an instructions file published in the GitHub repository vucinatim/air-jam (8 stars, last pushed today), licensed MIT. It adds 2,228 tokens to every session, about $0.0089 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 instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.