Borrowing it
Nothing to install: this file belongs to rumi-chan/league-client-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/rumi-chan/league-client-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/rumi-chan/league-client-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/rumi-chan/league-client-mcp/agents-md)<a href="https://agentmods.dev/instructions/rumi-chan/league-client-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/rumi-chan/league-client-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.06726 | $0.06726 |
| Opus 5 | $0.03363 | $0.03363 |
| Sonnet 5 | $0.01345 | $0.01345 |
| Haiku 4.5 | $0.00673 | $0.00673 |
Grade A, and why
league-client-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 6d 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 — 568 lines — stays where its author put it; the contents beside it link to each section on GitHub.
League Client MCP — Agent Instructions
Recognized by: OpenAI Codex CLI, OpenCode, Cursor, Windsurf, Aider, and any agent that reads
AGENTS.mdfrom the project root.
You are working with a live League of Legends Client via the league-client-mcp MCP server.
The server bridges AI tool calls to a Pengu Loader plugin running inside the LoL Client
(CEF/Chromium) over WebSocket at ws://127.0.0.1:8080.
Architecture
AI Agent ──MCP stdio──► MCP Server (Node.js)
│ WebSocket ws://127.0.0.1:8080
▼
Pengu Loader Plugin (inside LoL Client)
│ DOM · CSS · JS · LCU fetch()
▼
League of Legends Client (CEF / Chromium / Ember.js)
Prerequisites: League of Legends must be running with Pengu Loader active. The plugin auto-connects on client load. All 16 tools will be unavailable until the plugin connects.
Standard Workflow
1. get_lol_dom_snapshot → map the current page (selectors, component hierarchy)
2. inject_lol_css → prototype visual changes instantly (replaced on each call)
3. query_lol_element → verify selector, computed style, or bounding rect
4. inject_lol_plugin → add persistent JS behaviour with optional CSS
5. reload_lol_plugin → iterate after updating code (teardown + re-execute)
6. export_plugin_to_pengu → write finished plugin to disk as a Pengu Loader module
7. reload_lol_client → activate the exported plugin permanently
Tool Reference
DOM Inspection
get_lol_dom_snapshot
Returns a sanitized HTML snapshot of the active page. SVG path data, data-* attributes,
inline event handlers, and long src/href values are stripped to keep output lean.
Start every session here to discover selectors before writing any CSS or JS.
No parameters.
query_lol_element
Returns tag, text content, bounding rect, and computed styles for one specific element. Use this when you already know the selector and just need to verify it — much faster than a full snapshot.
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.
- 6d ago First seen · 568 lines · 6,726 tokens per session scan A ab360274820f
league-client-mcp AGENTS.md is an instructions file published in the GitHub repository rumi-chan/league-client-mcp (20 stars, last pushed 5mo ago), licensed MIT. It adds 6,726 tokens to every session, about $0.0336 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
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 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).
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.
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.