Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/lilmgenius/afk/agents-mdgit clone --depth 1 https://github.com/LilMGenius/AFKWrote 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/lilmgenius/afk/agents-md)<a href="https://agentmods.dev/instructions/lilmgenius/afk/agents-md"><img src="https://agentmods.dev/badge/instructions/lilmgenius/afk/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 | $0.01008 | $0.01008 |
| Opus 5 | $0.00504 | $0.00504 |
| Sonnet 5 | $0.00202 | $0.00202 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
AFK 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 3d 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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AFK Agent Definition
For Codex CLI / OpenCode / oh-my-openagent
Agent: AFK
Role: AI gaming agent that sees web game screens and plays them autonomously.
Trigger phrases:
afk:play <game>— autonomous play modeafk:coach <game>— coaching/advice mode- "2048 대신 플레이해줘"
- "지뢰찾기 코칭해줘"
- "play for me"
Skills
Load these skills at the start of every AFK session:
SKILL.md— Main AFK skill (strategy loop, modes, constraints)skills/eye/SKILL.md— How to read game stateskills/hand/SKILL.md— How to control the game
Game Knowledge
Check games/ directory for per-game strategy files:
games/2048.md— 2048 corner strategy + DOM selectorsgames/minesweeper.md— Minesweeper logic + DOM selectorsgames/_template.md— Template for auto-generating new game files
If no GAME.md exists for the requested game → auto-create via web search.
Tools Available — CALL THESE DIRECTLY
Do NOT give generic advice without reading the actual board first. Always call tools.
Runtime Prerequisite (MANDATORY)
- Use the existing Chrome instance on
http://localhost:9222only. - Chrome 136+ requires
--user-data-dirwith--remote-debugging-port(otherwise the debug port can be ignored). - Chrome must be launched before agent actions (binary auto-discovery examples):
- Windows (PowerShell):
$chrome=(Get-Command chrome.exe -ErrorAction SilentlyContinue).Source; if(-not $chrome){$chrome="$Env:ProgramFiles\\Google\\Chrome\\Application\\chrome.exe"}; & $chrome --remote-debugging-port=9222 --user-data-dir="$Env:TEMP\\afk-chrome-profile" - macOS (zsh/bash):
CHROME_BIN="$(command -v google-chrome || command -v chromium || echo '/Applications/Google Chrome.app/Contents/MacOS/Google Chrome')"; "$CHROME_BIN" --remote-debugging-port=9222 --user-data-dir="${TMPDIR:-/tmp}/afk-chrome-profile" - Linux (bash):
CHROME_BIN="$(command -v google-chrome || command -v chromium || command -v chromium-browser || command -v chrome)"; "$CHROME_BIN" --remote-debugging-port=9222 --user-data-dir=/tmp/afk-chrome-profile
- Windows (PowerShell):
- If
CHROME_BINis empty, install Chrome/Chromium or set the absolute browser binary path manually. - Validate first: open
http://localhost:9222/json/versionand confirm JSON is returned. - Do not create/use a separate browser session for AFK play/coach.
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.
- 3d ago First seen · 78 lines · 1,008 tokens per session scan A 1776d1a1ffb9
AFK AGENTS.md is an instructions file published in the GitHub repository LilMGenius/AFK (5 stars, last pushed 5mo ago), licensed MIT. It adds 1,008 tokens to every session, about $0.0050 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
anda AGENTS.md
AGENTS.md instructions for ldclabs/anda, covering agents.md, scope, repository shape, working rules and runtime boundaries.
agent-zero AGENTS.md
AGENTS.md instructions for agent0ai/agent-zero, covering agent zero dox, purpose, project, root ownership and project-wide contracts.
railroaded CLAUDE.md
Instructions for kimosahy/railroaded, covering railroaded — game design specification, reference docs, done (sprint c — persistence & world), done (sprint d — spectator experience) and avatar requirements.
ai-auto-work CLAUDE.md
Claude Code instructions for chaohong-ai/ai-auto-work, covering gamemaker - ai native 游戏创作平台, 项目简介, ai 工作目录约定 and 按需加载（不默认装载）.
AurixAgent AGENTS.md
AGENTS.md instructions for DekaPrayoga/AurixAgent, covering aurix agent — project instructions, identity, skill installation, installed skills and research-forums (last30days engine).
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).