Borrowing it
Nothing to install: this file belongs to DeepBlueCoding/mcp-replay-dota2. 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/DeepBlueCoding/mcp-replay-dota2/master/AGENTS.mdgit clone --depth 1 https://github.com/DeepBlueCoding/mcp-replay-dota2Wrote 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/deepbluecoding/mcp-replay-dota2/agents-md)<a href="https://agentmods.dev/instructions/deepbluecoding/mcp-replay-dota2/agents-md"><img src="https://agentmods.dev/badge/instructions/deepbluecoding/mcp-replay-dota2/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/deepbluecoding/mcp-replay-dota2/agents-md"><img src="https://agentmods.dev/badge/instructions/deepbluecoding/mcp-replay-dota2/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.00672 | $0.00672 |
| Opus 5.5 | $0.00269 | $0.00269 |
| Sonnet 5.5 | $0.00134 | $0.00134 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
mcp-replay-dota2 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 — 27 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Guidelines
Project Structure & Module Organization
src/ holds runtime modules: resources/ surfaces MCP-ready data (for example heroes_resources.py), tools/ wraps FastMCP utilities, and utils/ provides shared helpers for constants, fuzzy search, and replays. Root scripts (dota_match_mcp_server.py, main.py) are the entry points; data caches and artifacts live in data/, while maintenance helpers (like scripts/fetch_constants.py) keep them current. Primary tests live in tests/, and pytest still collects legacy root files such as test_fuzzy_search.py.
Build, Test, and Development Commands
uv sync # install pinned Python 3.12 environment
uv run python dota_match_mcp_server.py # launch the stdio FastMCP server
uv run python main.py # smoke test the package entry point
uv run pytest # execute the suite with pytest.ini settings
uv run python scripts/fetch_constants.py # refresh dotaconstants caches in data/
Use uv run so imports resolve inside the managed venv.
Coding Style & Naming Conventions
Stick to 4-space indentation, type hints, and docstrings as shown in src/utils/hero_fuzzy_search.py. Prefer snake_case functions, CapWords classes, and SCREAMING_SNAKE_CASE constants (see src/utils/constants.py). Keep FastMCP resource IDs in the dota2:// namespace, ensure regenerated JSON stays lowercase_with_underscores, and wire any formatter or linter through pyproject.toml so it can run via uv run.
Testing Guidelines
pytest.ini scopes discovery to tests/ plus test_*.py, enables verbose output, short tracebacks, and strict marker validation. Mirror the production layout for new tests (e.g., tests/test_heroes_resources.py), quarantine replay fixtures under data/fixtures/, and tag network- or replay-heavy suites with @pytest.mark.integration or @pytest.mark.slow. Gate those locally through uv run pytest -m "not slow" and favor assertions that validate hero IDs, alias coverage, and replay parsing results.
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 First seen · 27 lines · 672 tokens per session scan A 7257f5ea58b8
mcp-replay-dota2 AGENTS.md is an instructions file published in the GitHub repository DeepBlueCoding/mcp-replay-dota2 (3 stars, last pushed 4mo ago), licensed MIT. It adds 672 tokens to every session, about $0.0027 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).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.