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 instructions/vantage-sh/vantage-mcp-server/agents-mdgit clone --depth 1 https://github.com/vantage-sh/vantage-mcp-serverWrote 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/vantage-sh/vantage-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/vantage-sh/vantage-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/vantage-sh/vantage-mcp-server/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 | $0.01411 | $0.01411 |
| Opus 5 | $0.00705 | $0.00705 |
| Sonnet 5 | $0.00282 | $0.00282 |
| Haiku 4.5 | $0.00141 | $0.00141 |
Grade A, and why
vantage-mcp-server 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 5d 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Working notes for agents in this repo. The README covers setup and deployment; this file routes you to the right guide for code changes and lists the traps that are not obvious from a quick file scan.
This file is not a recipe. Step-by-step instructions live in the skills and subsystem READMEs linked below. Do not reconstruct conventions from neighboring files — much of the existing code predates current conventions.
Start here
| Task | Read first |
|---|---|
| Adding or changing a tool | .agents/skills/writing-mcp-tools/SKILL.md |
| Adding or changing an eval | .agents/skills/writing-evals/SKILL.md |
| Adding or changing MCP resources (VQL docs) | src/resources/README.md |
| Setup, client config, worker deployment | README.md |
New tools must ship with a matching unit test under test/ (testTool). Evals are opt-in: ask whether the user wants them included and, if so, whether the provider API key they intend to use is configured in the ignored .env file. Use the writing-evals skill only after the user opts in. Existing tools mostly predate evals — do not backfill or update evals unless asked. Opting in to eval authoring does not authorize a model-backed run; execution requires explicit approval and confirmation that the required API key is configured.
What this file does not cover
- MCP client configuration (Claude, Cursor, etc.) — README
- Cloudflare Worker / OAuth deployment — README and Wrangler config
- Resource authoring details —
src/resources/README.md - Fixing convention drift in unrelated PRs — see "Known drift" below
How tools plug in
Every tool file's default export is a registerTool({...}) call (src/tools/structure/registerTool.ts). Tools become live by being imported — that is all src/tools/index.ts does. The index is generated by npm run generate-tools-index; test/tools/index.test.ts fails CI if it is stale.
New tools go under src/tools/<resource>/, not at the top level of src/tools/. Add import "./<verb>-<resource>"; to the resource's index.ts, then run npm run generate-tools-index. Never hand-edit src/tools/index.ts.
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.
- 5d ago First seen · 72 lines · 1,411 tokens per session scan A 481abcf18ce5
vantage-mcp-server AGENTS.md is an instructions file published in the GitHub repository vantage-sh/vantage-mcp-server (84 stars, last pushed yesterday), licensed MIT. It adds 1,411 tokens to every session, about $0.0071 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
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).
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.
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 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.