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 skills/deepbluecoding/mcp-replay-dota2/write-mkdocs-docsnpx skills add DeepBlueCoding/mcp-replay-dota2 --skill write-mkdocs-docsgit clone --depth 1 https://github.com/DeepBlueCoding/mcp-replay-dota2What 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.00131 | $0.01102 |
| Opus 5 | $0.00066 | $0.00551 |
| Sonnet 5 | $0.00026 | $0.00220 |
| Haiku 4.5 | $0.00013 | $0.00110 |
Grade A, and why
write-mkdocs-docs 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 2d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write mkdocs docs for mcp-replay-dota2
CLAUDE.md (repo root) makes this MANDATORY: every feature/bugfix must (1) add a real-values
test, (2) update docs/api/tools/, (3) add an entry to docs/changelog.md. This skill is the
docs half.
Site stack: mkdocs-material + mike for versioning, deployed to gh-pages. Install docs deps via
the docs dependency-group (mkdocs-material, mike, mkdocstrings[python]).
Where a tool doc goes (by category, NOT by source module)
| Page | Covers |
|---|---|
docs/api/tools/match-analysis.md |
download/delete_replay, hero_deaths, hero_performance, combat log, item purchases, objective kills, match_timeline/info/heroes/players, runes, courier, draft |
docs/api/tools/game-state.md |
list_fights, get_teamfights, get_fight, camp_stacks, jungle_summary, snapshot_at_time, hero_positions, position_timeline, fight_replay |
docs/api/tools/farming-rotation.md |
get_farming_pattern, get_rotation_analysis |
docs/api/tools/lane-analysis.md |
lane_summary, cs_at_minute |
docs/api/tools/pro-scene.md |
search_pro_player, search_team, get_pro_matches, get_league_matches, etc. |
Per-tool section template
## get_hero_performance
One-line purpose of what the tool answers.
\`\`\`python
result = await client.call_tool("get_hero_performance", {
"match_id": 8594217096,
"hero": "pugna",
})
\`\`\`
**Returns:**
\`\`\`json
{ "...": "real-shaped JSON" }
\`\`\`
Also update docs/api/tools/index.md: add the tool to the "AI Summary - Tool Selection Guide"
admonition table and bump the per-category tool count in the Categories table. (The matching LLM
instruction in dota_match_mcp_server.py::TOOL_INSTRUCTIONS is updated by the add-mcp-tool
skill — keep both in sync.)
Adding a NEW page
The nav in mkdocs.yml is fully manual — a page not listed under nav: 404s. Add it under the
right section (API Reference > Tools lists the five tool pages today). Editing under docs/** or
mkdocs.yml is what makes docs.yml redeploy.
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.
- 2d ago First seen · 90 lines · 131 tokens per session scan A 4b61beaeed30
write-mkdocs-docs is a skill published in the GitHub repository DeepBlueCoding/mcp-replay-dota2 (2 stars, last pushed 2mo ago), licensed MIT. It adds 131 tokens to every session and 1,102 once invoked, about $0.0007 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…