Borrowing it
Nothing to install: this file belongs to Enovatr-Labs/SpecRoute. 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/Enovatr-Labs/SpecRoute/main/AGENTS.mdgit clone --depth 1 https://github.com/Enovatr-Labs/SpecRouteWrote 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/enovatr-labs/specroute/agents-md)<a href="https://agentmods.dev/instructions/enovatr-labs/specroute/agents-md"><img src="https://agentmods.dev/badge/instructions/enovatr-labs/specroute/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/enovatr-labs/specroute/agents-md"><img src="https://agentmods.dev/badge/instructions/enovatr-labs/specroute/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.02906 | $0.02906 |
| Opus 5 | $0.01453 | $0.01453 |
| Sonnet 5 | $0.00581 | $0.00581 |
| Haiku 4.5 | $0.00291 | $0.00291 |
Grade A, and why
SpecRoute 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 9d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Canonical, vendor-neutral context file for SpecRoute. This is the single source of truth for every agent CLI working in this repository.
Not every CLI loads it automatically. Codex and Cursor read AGENTS.md natively; Claude Code does not - its documentation states plainly that it reads CLAUDE.md, not AGENTS.md - and Gemini CLI does not either, since it reads GEMINI.md and only picks up AGENTS.md if you opt in through context.fileName. So CLAUDE.md and GEMINI.md are short delegation shims that pull this file in (an @AGENTS.md import, or a symlink). Blog posts claiming universal native AGENTS.md support are wrong; the shim is what makes it universal here.
About the AGENTS.md convention
AGENTS.md began as an OpenAI convention and is now stewarded by the Agentic AI Foundation under the Linux Foundation, with 60,000+ repositories using it. The convention specifies no required fields, no frontmatter, and no schema - it is plain Markdown, and its content is entirely up to the project. Nested AGENTS.md files are spec'd behaviour: an agent reads the nearest one up the directory tree.
What this repository is
SpecRoute is an open-source framework for spec-driven agentic software engineering, vendor-neutral across Claude Code, Codex, Gemini CLI, Kiro, Cursor, and Devin Desktop. It ships markdown content - templates, prompts, agent definitions, runtime layouts, and engineering rules - not application code.
There is no package manager, no build step, no test suite, no lint config. Do not look for package.json or run tests; treat this as a documentation/templates repository.
What "spec-driven" means here
The canonical flow is:
PRD → Spec (requirements + design + tasks) → Implementation → Validation → Review
Each stage has a template, an agent assignment, and an acceptance criterion. The point is not to slow work down - it's to make agent output reviewable. Code generation without a written spec is the failure mode this framework exists to prevent.
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.
- 9d ago First seen · 114 lines · 2,906 tokens per session scan A f5f008eebe7b
SpecRoute AGENTS.md is an instructions file published in the GitHub repository Enovatr-Labs/SpecRoute (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 2,906 tokens to every session, about $0.0145 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.