Borrowing it
Nothing to install: this file belongs to rigour-labs/rigour. 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/rigour-labs/rigour/main/AGENTS.mdgit clone --depth 1 https://github.com/rigour-labs/rigourWrote 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/rigour-labs/rigour/agents-md)<a href="https://agentmods.dev/instructions/rigour-labs/rigour/agents-md"><img src="https://agentmods.dev/badge/instructions/rigour-labs/rigour/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/rigour-labs/rigour/agents-md"><img src="https://agentmods.dev/badge/instructions/rigour-labs/rigour/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.00517 | $0.00517 |
| Opus 5.5 | $0.00207 | $0.00207 |
| Sonnet 5.5 | $0.00103 | $0.00103 |
| Haiku 4.5 | $0.00052 | $0.00052 |
Grade A, and why
rigour 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 18d 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 — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent instructions
Rigour is a pnpm monorepo: packages/rigour-core (checks, review, the reviewer), rigour-cli (the rigour
command, hooks, Studio's server), rigour-mcp (the MCP server) and rigour-studio (Studio's web page, built
into packages/rigour-cli/studio-dist). Node 22.13 or later.
Build and test
pnpm install
pnpm build # every package; core first if you only rebuild one
pnpm --filter @rigour-labs/core test # or cli, mcp, studio; `pnpm test` runs them all
pnpm --filter @rigour-labs/cli exec tsc --noEmit
A change to core is seen by the CLI and MCP only after core is rebuilt. A change to Studio ships only after
pnpm --filter @rigour-labs/cli build, which copies it into studio-dist; commit that output too.
Rules for this repository
- Every change comes with tests next to the code (
*.test.ts). Tests never touch a real home directory:vitest.setup.tspointsRIGOUR_HOMEandRIGOUR_AGENT_HOMEat throwaway folders; keep it that way. - A
rigour.ymlsetting exists only if code reads it. Adding or removing one means updatingscripts/docs/config-descriptions.json; the configuration reference is generated from the schema and checked in CI. - Pull request titles follow conventional commits and drive the release:
fix:by default,feat:only for something a user could not do before. - Docs describe what the code does today. A claim the code does not make true is a bug.
Rigour
This repository uses Rigour on itself. Its hooks check your work after each edit, before you finish and before a push.
- Before you say a task is done,
rigour review --base origin/main(or therigour_reviewMCP tool) must show nothing to fix. Fix what it reports in your change. - Before writing a new helper, ask
rigour_check_patternwhether one already exists. - Never edit
rigour.yml, add an ignore, or dismiss a finding to make a check pass. Whether a finding is wrong is a person's call. - Never push with
--no-verify.
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.
- 18d ago Changed · -209 lines · -1,476 tokens per session 4c15ac6be794
- 1mo ago First seen · 247 lines · 1,993 tokens per session scan A a466fb714c3f
rigour AGENTS.md is an instructions file published in the GitHub repository rigour-labs/rigour (29 stars, last pushed 6d ago), licensed MIT. It adds 517 tokens to every session, about $0.0021 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-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).
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).
vscode design-tokens.instructions.md
Design-system size tokens (spacing, corner radius, font size, codicon size, stroke). Use when writing or editing CSS to size, space, or round UI — prefer the --vscode- token vars over hardcoded px values.