undercover AGENTS.md

Repository instructions for an optional undercover mode that removes certain AI-like patterns from changed code and commit messages before public contributions.

In plain words
What is it for?
Use it when asked to go undercover, clean changes before a public pull request, or review staged files and commit messages before committing.
Why use it?
It helps prepare contributions that should read as naturally human-authored while preserving program logic and important explanatory comments.

Instructions file for CodexOpenCode

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/anasfik/undercover/agents-md
Clone the repo
git clone --depth 1 https://github.com/anasfik/undercover

Made for: Codex, OpenCode.

Per session 1,161 This file is loaded in full into every session.
When invoked 1,161 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01161 $0.01161
Opus 5 $0.00580 $0.00580
Sonnet 5 $0.00232 $0.00232
Haiku 4.5 $0.00116 $0.00116

Measured 2d ago against content hash 01054c27f15e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

AGENTS.md · 161 lines

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

Read the full file on GitHub · 161 lines

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.

  1. 2d ago First seen · 161 lines · 1,161 tokens per session scan A 01054c27f15e

Subscribe to this mod's changes

undercover AGENTS.md is an instructions file published in the GitHub repository anasfik/undercover (2 stars, last pushed 5mo ago), licensed MIT. It adds 1,161 tokens to every session, about $0.0058 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.