Borrowing it
Nothing to install: this file belongs to lsampaioweb/ai-instructions. 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/lsampaioweb/ai-instructions/main/.github/instructions/review-suppressions.instructions.mdgit clone --depth 1 https://github.com/lsampaioweb/ai-instructionsWrote 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/lsampaioweb/ai-instructions/review-suppressions)<a href="https://agentmods.dev/instructions/lsampaioweb/ai-instructions/review-suppressions"><img src="https://agentmods.dev/badge/instructions/lsampaioweb/ai-instructions/review-suppressions/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/lsampaioweb/ai-instructions/review-suppressions"><img src="https://agentmods.dev/badge/instructions/lsampaioweb/ai-instructions/review-suppressions.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.00407 | $0.00407 |
| Opus 5 | $0.00204 | $0.00204 |
| Sonnet 5 | $0.00081 | $0.00081 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
ai-instructions review-suppressions.instructions.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 7d 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.
What it actually says
Review Suppressions Registry
Rules
- Treat each Active Suppressions row with Status
activeand a future Expiry as a hard do-not-report match forreview-code-against-instructions. - Match suppressions by Path (exact file or glob) plus Rule (instruction file and bullet quote/anchor).
- Prefer narrowing the cited instruction or adding domain
## Approved Exception Handlingbefore adding a suppression row. - Require ID, Path, Rule, Reason, Owner, Expiry (
YYYY-MM-DD), and Status on every Active Suppressions row. - Use Status values
activeorexpiredonly. - Expire rows on Expiry: set Status to
expiredand do not honor them. - Keep IDs stable as
SUP-NNN(zero-padded), never reuse an ID for a different dismissal. - Record the user-confirmed reason; do not invent dismissals during a review.
Active Suppressions
| ID | Path | Rule | Reason | Owner | Expiry | Status |
|---|---|---|---|---|---|---|
| — | — | — | No active suppressions yet. Add a row after an explicit user dismissal. | — | — | — |
Safety Guards
- Never invent suppressions during a review without explicit user confirmation.
- Never honor a row whose Expiry is in the past or whose Status is not
active. - Never use this registry alone to silence Critical security findings; require an Approved Exception in the owning domain instruction file.
- Never broaden a Path or Rule match beyond the user’s confirmed dismissal scope.
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.
- 7d ago First seen · 29 lines · 407 tokens per session scan A 7fe17b4c6fc0
ai-instructions review-suppressions.instructions.md is an instructions file published in the GitHub repository lsampaioweb/ai-instructions (1 stars, last pushed 18d ago), licensed MIT. It adds 407 tokens to every session, about $0.0020 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-09-03.
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).
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.
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).