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/miscusi-peek/cheatengine-mcp-bridge/agents-mdgit clone --depth 1 https://github.com/miscusi-peek/cheatengine-mcp-bridgeWrote 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/miscusi-peek/cheatengine-mcp-bridge/agents-md)<a href="https://agentmods.dev/instructions/miscusi-peek/cheatengine-mcp-bridge/agents-md"><img src="https://agentmods.dev/badge/instructions/miscusi-peek/cheatengine-mcp-bridge/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.02256 | $0.02256 |
| Opus 5 | $0.01128 | $0.01128 |
| Sonnet 5 | $0.00451 | $0.00451 |
| Haiku 4.5 | $0.00226 | $0.00226 |
Grade A, and why
cheatengine-mcp-bridge 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 4d 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.
Copies of this mod
3 near-identical copies found in the catalogue:
- cheatengine-mcp-tcp-bridge AGENTS.md — 100% identical, 0 lines differ
- cheatengine-mcp-bridge CLAUDE.md — 91% identical, 4 lines differ
- cheatengine-mcp-tcp-bridge CLAUDE.md — 91% identical, 4 lines differ
How it starts
The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file provides guidance to Codex (Codex.ai/code) when working with code in this repository.
What this project is
A three-tier bridge that lets AI agents (via MCP) drive Cheat Engine to inspect and manipulate a running Windows process. See README.md for user-facing docs. Current wire/app version: 12.0.0. After the v12 overhaul the bridge exposes ~180 MCP tools covering memory, process lifecycle, code injection, symbol management, assembly/compilation, GUI automation, input, cheat tables, and kernel-mode operations.
Commands
# Install Python deps (Windows only — uses pywin32)
pip install -r MCP_Server/requirements.txt
# Integration test suite (requires: CE running, ce_mcp_bridge.lua loaded, a process attached)
python MCP_Server/test_mcp.py
Loading the Lua side in Cheat Engine: File -> Execute Script -> open MCP_Server/ce_mcp_bridge.lua -> Execute. Some CE builds expose this through Table -> Show Cheat Table Lua Script; in that case execute dofile([[C:\path\to\cheatengine-mcp-bridge\MCP_Server\ce_mcp_bridge.lua]]) instead of pasting the full bridge. Success log: [MCP v12.0.0] MCP Server Listening on: CE_MCP_Bridge_v99. Re-executing the script auto-calls StopMCPBridge / cleanupZombieState first, so reloading is safe.
There is no build step, no linter, and no unit-test harness. test_mcp.py is a single end-to-end script that talks to the live Named Pipe; running a "single test" means editing the all_tests dict in test_mcp.py:main or commenting out sections.
The MCP server is normally spawned by the AI client over stdio, but can be launched directly with python MCP_Server/mcp_cheatengine.py for debugging (it blocks waiting for stdio JSON-RPC).
Architecture
Three processes, two IPC layers:
AI client ──(MCP / JSON-RPC over stdio)──▶ mcp_cheatengine.py
│
▼ (length-prefixed JSON-RPC)
\\.\pipe\CE_MCP_Bridge_v99
│
▼
ce_mcp_bridge.lua (inside Cheat Engine)
│
▼ (CE Lua API / DBVM)
Target process memory
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.
- 4d ago First seen · 103 lines · 2,256 tokens per session scan A d61b6ae6842c
cheatengine-mcp-bridge AGENTS.md is an instructions file published in the GitHub repository miscusi-peek/cheatengine-mcp-bridge (1,370 stars, last pushed 21d ago), licensed MIT. It adds 2,256 tokens to every session, about $0.0113 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
GameDesignOS AGENTS.md
Instructions for DY-2026/GameDesignOS, covering gamedesignos agent 入口, 默认接法, agent 执行规则, 什么时候用整个项目 and 每个 skill 单独怎么用.
detroit-ai-player AGENTS.md
Instructions for Baba88611/detroit-ai-player, covering agents.md — 给 ai agent 的部署与运行指引, 这是什么, 前置检查, 装依赖 and 选后端（决策树，按顺序判断）.
detroit-ai-player CLAUDE.md
Instructions for Baba88611/detroit-ai-player, covering detroit: become human — ai 自主决策实验, 项目目标, 实验概述, 项目结构 and 阶段依赖与推进顺序.
cheatengine-mcp-tcp-bridge CLAUDE.md
Instructions for HollyZoe/cheatengine-mcp-tcp-bridge, covering claude.md, what this project is, commands, install python deps (windows only — uses pywin32) and architecture.
cheatengine-mcp-tcp-bridge AGENTS.md
Instructions for HollyZoe/cheatengine-mcp-tcp-bridge, covering agents.md, what this project is, commands, install python deps (windows only — uses pywin32) and architecture.
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).