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/xayan/ast-outline-mcp/agents-mdgit clone --depth 1 https://github.com/Xayan/ast-outline-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/xayan/ast-outline-mcp/agents-md)<a href="https://agentmods.dev/instructions/xayan/ast-outline-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/xayan/ast-outline-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.00679 | $0.00679 |
| Opus 5 | $0.00340 | $0.00340 |
| Sonnet 5 | $0.00136 | $0.00136 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
ast-outline-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 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Overview
MCP server wrapping the ast-outline CLI (uv tool install ast-outline) as 4 tools: outline, digest, show, grep. Single ESM TypeScript package, no monorepo.
Commands
| Command | What |
|---|---|
npm run build |
tsc — compiles src/ → dist/ |
npm test |
jest --config jest.config.cjs — all tests |
npm run lint |
eslint src tests --max-warnings 0 — will fail on any warning |
npm start |
node dist/index.js — stdio MCP server |
npm run start:http |
node dist/server/http-server.js — SSE on :3001/sse |
npm run dev |
tsc --watch |
Run build && lint && test after making changes.
Architecture
src/index.ts— CLI entrypoint, startsFastMCPon stdiosrc/server/http-server.ts— HTTP entrypoint, SSE transport on:3001src/server/server.ts— createsFastMCPinstance, wires up tools/prompts/resourcessrc/core/tools.ts— registers 4 tools, each delegates toAstOutlineServicesrc/core/prompts.ts— registersexplore-codebasepromptsrc/core/services/ast-outline-service.ts— shells out toast-outlinebinary viaexecFile- No static resources (stateless by design)
- Binary path and timeout configurable via
AstOutlineOptions(defaults:"ast-outline", 30s)
Key constraints
- Requires
ast-outlineon PATH — install withuv tool install ast-outline - Node >= 18,
"type": "module"(ESM) - Imports use
.jsextensions (TypeScriptNodeNextmodule resolution) - Tests mock
execFile— no real binary needed to run tests ast-outlineCLI returns exit code 0 even for user-facing failures; service handles this by checkingstdoutpresence before reporting errors
Testing quirks
jest.config.cjs— ts-jest preset overridden tocommonjsmodule (tests tsconfig also overrides to commonjs)- Test file pattern:
**/tests/**/*.test.ts - Module name mapper strips
.jsfrom imports:"^(\\.{1,2}/.*)\\.js$": "$1" - Tests live in
tests/(notsrc/__tests__/)
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 · 54 lines · 679 tokens per session scan A f55d2405c92d
ast-outline-mcp AGENTS.md is an instructions file published in the GitHub repository Xayan/ast-outline-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 679 tokens to every session, about $0.0034 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
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).
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).
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.
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.
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.