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/kanonzombie/emulator-mcp/agents-mdgit clone --depth 1 https://github.com/KanonZombie/emulator-mcpWrote 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/kanonzombie/emulator-mcp/agents-md)<a href="https://agentmods.dev/instructions/kanonzombie/emulator-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/kanonzombie/emulator-mcp/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.00584 | $0.00584 |
| Opus 5 | $0.00292 | $0.00292 |
| Sonnet 5 | $0.00117 | $0.00117 |
| Haiku 4.5 | $0.00058 | $0.00058 |
Grade A, and why
emulator-mcp 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 5d 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 — 36 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
server/mcp_server.pycontains the MCP tools, CLI entry point, scenario runner, and file-based BizHawk protocol.server/gb_gpu_renderer.pyrenders Game Boy diagnostic snapshots.bizhawk/bridge.luais the portable script loaded by BizHawk.scenarios/{gb,md,nes,snes}/stores target-specific JSON flows;scenarios/pairs/stores GB/Mega Drive comparisons.server/tests/contains unit tests and the opt-in BizHawk smoke runner.runtime/,build/,dist/, virtual environments, and.emulator-mcp/are generated and must remain untracked.
Build, Test, and Development Commands
Run these from the repository root on Windows:
python -m venv .venv
.\.venv\Scripts\python.exe -m pip install .
.\.venv\Scripts\python.exe -m unittest discover -s server\tests -v
.\.venv\Scripts\python.exe -m pip wheel . --no-deps -w dist
The installation exposes emulator-mcp; the test command needs no emulator; the wheel command verifies packaging. For release-level bridge checks, run .\.venv\Scripts\python.exe server\tests\bizhawk_smoke.py --bizhawk <EmuHawk.exe> with BizHawk installed.
Coding Style & Naming Conventions
Use Python 3.10+ syntax, four-space indentation, type hints on public functions, snake_case for functions and files, PascalCase for classes, and uppercase constants. Group imports as standard library, third party, then local modules. Match the existing straightforward Lua style in bridge.lua. Name scenarios with lowercase snake case and IDs such as nes.title_start. No formatter or linter is configured; keep diffs focused and follow surrounding code.
Testing Guidelines
Tests use unittest. Put files under server/tests/ as test_*.py, methods as test_*, and isolate filesystem or environment changes with temporary directories and mocks. Add one focused regression test for non-trivial behavior. No coverage threshold is configured. Changes to the bridge or target handling should also pass the relevant BizHawk smoke target.
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.
- 5d ago First seen · 36 lines · 584 tokens per session scan A a961cc4a357d
emulator-mcp AGENTS.md is an instructions file published in the GitHub repository KanonZombie/emulator-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 584 tokens to every session, about $0.0029 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
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).
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.
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 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.