Borrowing it
Nothing to install: this file belongs to abagames/claude-one-button-game-creation. 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/abagames/claude-one-button-game-creation/main/AGENTS.mdgit clone --depth 1 https://github.com/abagames/claude-one-button-game-creationWrote 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/abagames/claude-one-button-game-creation/agents-md)<a href="https://agentmods.dev/instructions/abagames/claude-one-button-game-creation/agents-md"><img src="https://agentmods.dev/badge/instructions/abagames/claude-one-button-game-creation/agents-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.1 | $0.00891 | $0.00891 |
| Opus 5 | $0.00445 | $0.00445 |
| Sonnet 5 | $0.00178 | $0.00178 |
| Haiku 4.5 | $0.00089 | $0.00089 |
Grade A, and why
claude-one-button-game-creation 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 7d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
claude-one-button-game-creation
An automatic one-button game generation project using crisp-game-lib. Agents use random tags as inspiration to design and implement a varied batch of ten browser-playable games.
The standard workflow ends when ten runnable games are presented. Ranking, selection, human review, Polish, retrospective, publication, and play-log mechanical evaluation are separate activities and require an explicit user request.
Working Directory
Run all commands from the project root (the directory containing this file).
- Generation workflow:
./workflows/game-generation.md - Scripts:
./scripts/ - Static tag inputs:
./data/ - Generated games:
./tmp/games/
On a fresh clone, run:
npm ci
npm run skills:install
npm run playwright:install
npm test
skills:install copies only the skills required by this project from
abagames/agentic-gamedev-skills
into the ignored local .agents/skills/ directory. It replaces only those
three skill directories and preserves other content under .agents/. To
refresh intentionally, run the command again; set AGENT_SKILLS_REF to the
desired upstream commit. The generation workflow has no durable-state
initialization requirement.
Standard Flow: Generate and Present Ten Games
- Confirm
tmp/games/is absent or empty. If it contains anything, stop and ask the user what to do. Do not delete, overwrite, move, or archive existing output without explicit user direction. - Run
workflows/game-generation.mdonce per game with a fresh generation context and fresh tag seed. - Repeat until
tmp/games/contains exactly ten new games. - Smoke-test every game's
index.htmlin a real browser. Repair runtime failures and re-run the failed smoke test. - Present the ten games as an unranked list and stop.
Each game must be generated independently. A game-generation context may read the generation workflow, the relevant skills, its own tags, and its own output, but must not compare against other games in the batch or attempt to select a winner.
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.
- 7d ago First seen · 114 lines · 891 tokens per session scan A e79a4cba595f
claude-one-button-game-creation AGENTS.md is an instructions file published in the GitHub repository abagames/claude-one-button-game-creation (53 stars, last pushed 1mo ago), licensed MIT. It adds 891 tokens to every session, about $0.0045 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-30.
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.