Borrowing it
Nothing to install: this file belongs to caotrongphuoc/11m-game. 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/caotrongphuoc/11m-game/main/AGENTS.mdgit clone --depth 1 https://github.com/caotrongphuoc/11m-gameWrote 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/caotrongphuoc/11m-game/agents-md)<a href="https://agentmods.dev/instructions/caotrongphuoc/11m-game/agents-md"><img src="https://agentmods.dev/badge/instructions/caotrongphuoc/11m-game/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.02112 | $0.02112 |
| Opus 5 | $0.01056 | $0.01056 |
| Sonnet 5 | $0.00422 | $0.00422 |
| Haiku 4.5 | $0.00211 | $0.00211 |
Grade A, and why
11m-game 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 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.
How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AK firmware — agent instructions
This project is firmware for the AK (Active Kernel) event-driven MCU framework.
You have access to the ak-docs MCP server. Use it as the source of truth — do
not guess AK APIs from memory.
Starting a new project? If this is a fresh/empty workspace (no application/ yet),
call start_ak_project first — it downloads the latest base-kit release and gives you
the commands to lay it out. Run them, then customize per the steps below.
Before writing or changing any firmware:
- Call
get_ak_guardrailsfirst. Never modifyapplication/sources/ak/(kernel),boot/,application/sources/networks/, orapplication/sources/common/. Build features inapplication/sources/app/andapplication/sources/driver/only. - For a new task/driver/screen, call
get_ak_guide(create-task,create-driver,create-screen,use-timer,isr-bridge,tune-pools) and follow the steps and skeleton exactly. - For any kernel function/macro, call
get_ak_apito get the exact signature and arguments. Usesearch_ak_docswhen you don't know the symbol name.
Debugging a running board? All debugging is over the UART console (115200 8N1):
call get_ak_guide("debug-uart-shell") first. Capture output non-interactively with
python ak-console.py --port <P> --cmd "ver" --cmd "fatal l" (or --watch 15 for live
logs), then paste the raw text into analyze_ak_log and follow its Next steps.
For display issues, capture --cmd "lcd d" and paste the dump into decode_ak_lcd
to see the OLED contents.
Run only read-only shell commands on your own; destructive ones (reboot, fatal t/!/@/r,
ram r, eps r, flash i, boot r/t, fwu, dbg s) need the engineer's explicit OK.
Hard rules (also returned by get_ak_guardrails):
- Handlers must be non-blocking — no
delay(), no busy-wait. Use a timer that posts a signal instead. - Tasks communicate only via messages (
task_post_*), never direct calls or shared globals. - User signals start at
AK_USER_DEFINE_SIG(10); task priorities areLEVEL_1..7(0 is reserved). - Common message payload ≤ 64 bytes; max 7 references per message; pools are fixed size.
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 · 150 lines · 2,112 tokens per session scan A d1695ba6932d
11m-game AGENTS.md is an instructions file published in the GitHub repository caotrongphuoc/11m-game (2 stars, last pushed 10d ago), licensed MIT. It adds 2,112 tokens to every session, about $0.0106 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.