Borrowing it
Nothing to install: this file belongs to SunrisesIllNeverSee/bestuser-router-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/SunrisesIllNeverSee/bestuser-router-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/SunrisesIllNeverSee/bestuser-router-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/sunrisesillneversee/bestuser-router-mcp/agents-md)<a href="https://agentmods.dev/instructions/sunrisesillneversee/bestuser-router-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/sunrisesillneversee/bestuser-router-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/sunrisesillneversee/bestuser-router-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/sunrisesillneversee/bestuser-router-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.01335 | $0.01335 |
| Opus 5 | $0.00668 | $0.00668 |
| Sonnet 5 | $0.00267 | $0.00267 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
bestuser-router-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 4d 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository Operating Instructions
Startup order
Before creating, moving, renaming, or deleting files:
- Read
REPO.yaml. - Read this file.
- If coordination is enabled, read
.coord/micro/STATE.mdand the tail of.coord/micro/SCRATCHPAD.md. - If the work spans repositories, read
.coord/macro/LINK.yamland.coord/macro/MACRO_STATE.md. - Run
python3 .repo/scripts/repo_check.pybefore making structural changes to understand existing drift.
Root policy
Do not create a new root directory unless it is allowed by the selected .repo/profiles/<type>.json profile or explicitly added to REPO.yaml.
Do not place reports, design docs, PDFs, generated outputs, screenshots, exports, or temporary notes in root.
Canonical-document policy
Do not create _final, _new, _updated, _revised, _copy, numbered-copy, or similar versions of active documents. Update the canonical file or archive the superseded file with provenance.
Generated-output policy
Generated reports/results belong in the profile's artifact/result root, not alongside source.
Archive policy
Archive is provenance-preserving. Do not silently edit archived material. If an archived record must change, document why in the active coordination bus/handoff.
Micro coordination
Micro coordination lives under .coord/micro/.
- Before work: set a role and read state + scratchpad tail.
- During work: use the scratchpad for material task assignment, blockers, decisions, and handoff notes.
- Before stopping: save state and sign out.
Do not create alternate scratchpads or parallel hidden coordination buses.
Macro coordination
Macro coordination lives under .coord/macro/ and is used only when a build spans repositories/systems. It may point to a shared build hub. Do not use macro coordination as a permanent organization inventory.
Git behavior
- Prefer small, intentional commits.
- Do not force-push the protected default branch.
- Do not bypass repository validation just to merge.
- Structural moves should be isolated where practical so link/import breakage is reviewable.
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.
- 4d ago Changed · +54 lines · +416 tokens per session 422e97ad6f87
- 8d ago First seen · 97 lines · 919 tokens per session scan A 91d3804cdb6d
bestuser-router-mcp AGENTS.md is an instructions file published in the GitHub repository SunrisesIllNeverSee/bestuser-router-mcp (0 stars, last pushed 3d ago), licensed MIT. It adds 1,335 tokens to every session, about $0.0067 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.