Borrowing it
Nothing to install: this file belongs to anasfik/undercover. 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/anasfik/undercover/main/AGENTS.mdgit clone --depth 1 https://github.com/anasfik/undercoverWrote 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/anasfik/undercover/agents-md)<a href="https://agentmods.dev/instructions/anasfik/undercover/agents-md"><img src="https://agentmods.dev/badge/instructions/anasfik/undercover/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/anasfik/undercover/agents-md"><img src="https://agentmods.dev/badge/instructions/anasfik/undercover/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.01161 | $0.01161 |
| Opus 5.5 | $0.00464 | $0.00464 |
| Sonnet 5.5 | $0.00232 | $0.00232 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
undercover 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 1mo 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 — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Undercover Mode
You have an undercover mode available. When active, you automatically strip AI-characteristic patterns from code and commit messages before they are committed or pushed, so the contribution reads as natural, human-authored work.
When to activate
Activate undercover mode automatically (without being asked) when:
- The user says "go undercover", "undercover mode", "clean before PR", "strip AI signatures", "make this look human", "prep for open source", "clean commits", or any semantically equivalent phrase
- The user is about to commit to a public or open-source repository and you detect AI-characteristic patterns in staged or recently changed files
- The user asks you to "review before committing" on a public repo
What undercover mode does
Scan every staged or recently modified source file line by line and remove or rewrite any line that matches the patterns below. Then apply the same rules to the commit message.
Never touch: logic, strings, variable names, or comments that explain a non-obvious why (workarounds, hidden constraints, performance notes, subtle bug explanations).
Pattern rules
Apply these rules in order. For each matching line, take the listed action.
1. Step-numbered headers — REMOVE the line
Matches:
// Step 1: // Phase 2: // Part 3:
// Step 1. # Step 1: /* Step 1: */
2. Flow-narrating comments — REMOVE the line
Matches (case-insensitive at the start of a comment):
// First, we ... // Next, we ...
// Now we ... // Then we ...
// Finally, we ... // First, we need to ...
3. First-person-plural assistant phrases — REMOVE the line
Matches:
// Let's start by ... // Let's now ...
// We can now ... // We can use ...
// We need to ... // We should ...
// This will ... // This function will ...
4. Obvious restating comments — REMOVE the line
Matches (comment directly above or beside trivially named code):
// Get the X // Set the X
// Return the X // Fetch the X
// Check if X // Check whether X
// Initialize X // Initialize the X
// Define X // Create the X
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.
- 1mo ago First seen · 161 lines · 1,161 tokens per session scan A 01054c27f15e
undercover AGENTS.md is an instructions file published in the GitHub repository anasfik/undercover (2 stars, last pushed 6mo ago), licensed MIT. It adds 1,161 tokens to every session, about $0.0046 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.