Borrowing it
Nothing to install: this file belongs to projectcpu/project-cpu-mcp. 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/projectcpu/project-cpu-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/projectcpu/project-cpu-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/projectcpu/project-cpu-mcp/agents-md)<a href="https://agentmods.dev/instructions/projectcpu/project-cpu-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/projectcpu/project-cpu-mcp/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/projectcpu/project-cpu-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/projectcpu/project-cpu-mcp/agents-md.svg" alt="Reviewed on agentmods" width="80" 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.02641 | $0.02641 |
| Opus 5.5 | $0.01056 | $0.01056 |
| Sonnet 5.5 | $0.00528 | $0.00528 |
| Haiku 4.5 | $0.00264 | $0.00264 |
Grade A, and why
project-cpu-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 1mo 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 — 175 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project CPU MCP Server
MCP server for a blockchain game on EVM. Distributed via npm, runs locally via npx.
Two wallet modes via WALLET_MODE (defaults to paybox): paybox (browser OAuth and remote signing) or evm (private key in env, SIWE auth — requires PRIVATE_KEY). Session state persists to ~/.project-cpu/session.json.
The launch chain is Robinhood Chain (chainId 4663). NETWORK is optional, defaults to robinhood, and rejects every other value at startup. The default game API is https://api.projectcpu.cc; contract addresses are loaded from GET /api/v1/config?network=robinhood. Set RPC_URL to override the chain's public RPC when sending transactions (e.g. reveal).
Worktrees
ALWAYS work in a worktree for ANY change — no exceptions. The moment a task will touch a file
(code, config, workflow, docs, secrets — anything that gets committed), the FIRST action is to create
a worktree. The main checkout stays on main as a read-only hub; never edit, branch, or commit in
it. "It's a small/interactive/one-off change" is NOT an exception — every change goes through a
worktree. Read-only work (exploring, answering questions, running tests/builds) may stay in the hub.
Branches: <type>/<kebab-slug>, type — conventional-commit (feat fix chore refactor test
docs perf ci build revert); defaults to feat when no type is given.
- YOU MUST create or re-enter worktrees with
bash tools/harness/worktree-create.sh --name <type>/<slug> [--source PATH]. The command branches off the hub, copies local-only files, installs dependencies, and prints the absolute worktree path on stdout. Use that returned path as the working directory for every subsequent mutation. A name without a type becomesfeat/<slug>. Never usegit worktree adddirectly and never create a branch in the hub — both bypass the repository lifecycle. - Worktrees live in the sibling
../mcp-worktrees/<branch-slug>directory. - A new local-only (gitignored) file a worktree needs → add its path to
HARNESS_LOCAL_FILESintools/harness/worktree-common.shso creation and safe cleanup use the same inventory. - Remove a worktree with
bash tools/harness/worktree-cleanup.sh --target PATH [--source PATH]. Cleanup preserves local and unmerged work and keeps the branch by default. Installed dependencies and unchanged copies of the configured local files are reproducible lifecycle artifacts; changed local copies and all other ignored files remain protected. Use--discard-changesonly after an explicit decision to destroy detected work, and use the independent--delete-branchflag only after an explicit decision to remove the branch. Never finish cleanup with hand-written recursive deletion.
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.
- 1mo ago Changed · +2 lines · -2 tokens per session bf215863404b
- 1mo ago Changed · +3 tokens per session b03a13c481fd
- 1mo ago First seen · 173 lines · 2,640 tokens per session scan A ba1fc87446af
project-cpu-mcp AGENTS.md is an instructions file published in the GitHub repository projectcpu/project-cpu-mcp (1 stars, last pushed 13d ago), licensed MIT. It adds 2,641 tokens to every session, about $0.0106 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.