Borrowing it
Nothing to install: this file belongs to reasvyn/docsgrep. 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/reasvyn/docsgrep/main/AGENTS.mdgit clone --depth 1 https://github.com/reasvyn/docsgrepWrote 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/reasvyn/docsgrep/agents-md)<a href="https://agentmods.dev/instructions/reasvyn/docsgrep/agents-md"><img src="https://agentmods.dev/badge/instructions/reasvyn/docsgrep/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/reasvyn/docsgrep/agents-md"><img src="https://agentmods.dev/badge/instructions/reasvyn/docsgrep/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.00749 | $0.00749 |
| Opus 5.5 | $0.00300 | $0.00300 |
| Sonnet 5.5 | $0.00150 | $0.00150 |
| Haiku 4.5 | $0.00075 | $0.00075 |
Grade A, and why
docsgrep 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 2mo 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Quick Commands
pnpm install # install deps
pnpm build # compile TypeScript (tsc) → build/
pnpm test # vitest
pnpm test:coverage
Commands prefixed lint, audit, bugs, docs:check, docs:stale run docsgrep on itself (dogfooding). They require a prior pnpm build.
Repo Structure
Single-package TypeScript project (ESM).
src/index.ts— entry point (MCP server setup + plugin discovery, keep thin)src/cli.ts— CLI argument parsing and displaysrc/core-tools.ts— class-based tools (AnalyzeCodeTool, AuditSecurityTool, CatchBugsTool)src/tools/— tool handlers; one module per logical group:base.ts— BaseTool abstract class (semaphore, logging, credential masking)registry.ts— ToolRegistry (imports from split modules, self-registers core tools)doc-find.ts,doc-search.ts,doc-inspect.ts,doc-coverage.ts— documentation toolsdoc-verify.ts,doc-sync.ts— verification and sync toolshelp.ts,repo-analysis.ts,repo.ts— help, stack detection, cloneworkspace.ts— workspace init and cache managementarchetypes.ts,audit-ask.ts— pattern detection and interactive prompts
src/utils/— shared utilities (file scanning, git, validation, workspace, cache, logging)src/types/tools.ts— tool input interfacessrc/config/— JSON config for limits, patterns, language defstests/— Vitest test suites (tests/**/*.test.ts)docs/— project and tool documentation
Critical Conventions
- ESM with
.jsextensions: all local imports MUST include.js(e.g.,import { x } from "./utils.js"). - Strict TypeScript: no implicit
any. UseMcpToolResponsefor tool outputs. - BaseTool pattern: new tool handlers should extend
BaseToolfromtools/base.tsfor logging, credential masking, and concurrency limiting. - Scanning: use
FileScanner.findFilesfor filesystem scanning. Scanning tools must supportincludePath/excludePathand respect.gitignoreviagetIgnorePatternsfromutils/file.ts. - Validation: validate
dirPathinputs withvalidateDirPath. - App metadata: use
AppInfofromutils/app-info.ts, never hardcode version/name.
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.
- 2mo ago First seen · 59 lines · 749 tokens per session scan A 81b70cb702fc
docsgrep AGENTS.md is an instructions file published in the GitHub repository reasvyn/docsgrep (0 stars, last pushed 3mo ago), licensed MIT. It adds 749 tokens to every session, about $0.0030 per session on Opus 5.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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.