Borrowing it
Nothing to install: this file belongs to rajudandigam/agent-inspect. 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/rajudandigam/agent-inspect/main/AGENTS.mdgit clone --depth 1 https://github.com/rajudandigam/agent-inspectWrote 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/rajudandigam/agent-inspect/agents-md)<a href="https://agentmods.dev/instructions/rajudandigam/agent-inspect/agents-md"><img src="https://agentmods.dev/badge/instructions/rajudandigam/agent-inspect/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.01932 | $0.01932 |
| Opus 5 | $0.00966 | $0.00966 |
| Sonnet 5 | $0.00386 | $0.00386 |
| Haiku 4.5 | $0.00193 | $0.00193 |
Grade A, and why
agent-inspect 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 8d 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AgentInspect AI Maintainer Instructions
Product boundary
AgentInspect is the local evidence debugger and trajectory-test toolkit for TypeScript AI agents.
Primary loop: framework-native capture → faithful local execution tree → TraceFacts / TraceContract → deterministic trajectory gate → share-checked Evidence v2 → optional local read-only MCP.
Keep it local-first, CLI-first, TypeScript-first, safe by default, dependency-light, framework-native where possible, explicit about network behavior, and compatible with existing traces.
Do not turn it into hosted SaaS/APM, default telemetry upload, prompt/eval hosting, provider pricing, universal monkey-patching, raw chain-of-thought capture, or default replay/cassette execution.
Source of truth
Use this order:
- Git state, manifests, source, tests, fixtures
AGENTS.mddocs/implementation/RELEASE-TRAIN-STATE.mddocs/implementation/CURRENT-TASK.mddocs/implementation/ROADMAP.md(permanent canonical roadmap)docs/implementation/active/EXECUTION-PLAN.md- relevant ADR / security / public-evidence docs under
docs/decisions/anddocs/ - public
ROADMAP.md - compact
docs/history/summaries - Git tags / releases / history for full prior detail
Report material conflicts; never resolve them silently.
Named autonomous train authorized when CURRENT-TASK.md sets executionMode: "autonomous-release-train":
agentinspect-repository-health-evidence-ux-v6.16-to-pre-v7
Public-copy rule
Public surfaces present a mature, actively maintained product used in real TypeScript agent workflows. Never use “waiting for adoption,” “no adoption yet,” “test phase,” “pre-adoption,” or similar soft-launch framing. Never fabricate company names, logos, retention figures, ROI, or private traces.
Start every task
git status --short
git branch --show-current
git log -3 --oneline
git diff --check
Stop on unrelated uncommitted changes.
Read only the state file, current task, active plan chunk, and directly related source/tests. Do not reread the whole repository or full roadmap unless architecture or release direction changes.
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.
- 8d ago First seen · 221 lines · 1,932 tokens per session scan A ee766af76881
agent-inspect AGENTS.md is an instructions file published in the GitHub repository rajudandigam/agent-inspect (507 stars, last pushed yesterday), licensed MIT. It adds 1,932 tokens to every session, about $0.0097 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
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).
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.
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.