Borrowing it
Nothing to install: this file belongs to duckling1169/valorant-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/duckling1169/valorant-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/duckling1169/valorant-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/duckling1169/valorant-mcp/agents-md)<a href="https://agentmods.dev/instructions/duckling1169/valorant-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/duckling1169/valorant-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/duckling1169/valorant-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/duckling1169/valorant-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.00455 | $0.00455 |
| Opus 5 | $0.00228 | $0.00228 |
| Sonnet 5 | $0.00091 | $0.00091 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
valorant-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 9d 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 — 33 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project instructions
Commands
- Setup:
Node.js 24.x and pnpm 10.x are required; implementation has not started - Fast check:
sh scripts/check-agent-docs.sh - Full check:
sh scripts/check-agent-docs.sh - Build:
N/A — implementation has not started
Non-inferable rules
- HenrikDev is the sole VALORANT data provider. Use its current official documentation/OpenAPI; legacy repository documentation is comparison material only.
- Use TypeScript on Node.js 24.x with pnpm; do not rely on the locally installed Node.js 25 runtime for deployment compatibility.
- TypeScript runs in strict mode. Do not use
any,as unknown as, or unchecked assertion casts; validate untrusted API and request data at boundaries instead. - Do not implement, expose, or cache player-data flows whose consent scope or deployment approval is unresolved (M0 resolved for the operator's own data and matches, see ARCHITECTURE.md Decisions 2026-07-28; M3 multi-user access is its own unresolved gate).
- Keep MCP responses factual and token-efficient. Never add public lookup, prefetching, scraping, population-level analytics, or cross-player profile drill-down without explicit approved scope.
- Treat API keys, OAuth credentials, player identities, and match data as sensitive. Never commit or expose them.
Completion requirements
- Follow the shared workflow and escalation rules in
CONTRIBUTING.md. - Run the relevant checks above and report anything not run.
- Report observable behavior changed, validation results, and unresolved risks.
- Update an existing durable document only when the change makes it materially false. Do not create status logs or completed-work ledgers; Git history is the record.
Read on demand
README.md: purpose, setup, and normal use.ARCHITECTURE.md: before changing boundaries, contracts, or cross-component behavior.CONTRIBUTING.md: before non-trivial implementation or integration work; canonical shared contribution workflow.BACKLOG.md: when planning or resuming work, not for every task.ROADMAP.md: only when a task depends on longer-term direction.
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.
- 9d ago First seen · 33 lines · 455 tokens per session scan A 47f8fa5a23c0
valorant-mcp AGENTS.md is an instructions file published in the GitHub repository duckling1169/valorant-mcp (1 stars, last pushed 1mo ago), licensed MIT. It adds 455 tokens to every session, about $0.0023 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 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.
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.