Borrowing it
Nothing to install: this file belongs to nolindnaidoo/secrets-le. 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/nolindnaidoo/secrets-le/main/AGENTS.mdgit clone --depth 1 https://github.com/nolindnaidoo/secrets-leWrote 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/nolindnaidoo/secrets-le/agents-md)<a href="https://agentmods.dev/instructions/nolindnaidoo/secrets-le/agents-md"><img src="https://agentmods.dev/badge/instructions/nolindnaidoo/secrets-le/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/nolindnaidoo/secrets-le/agents-md"><img src="https://agentmods.dev/badge/instructions/nolindnaidoo/secrets-le/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.06782 | $0.06782 |
| Opus 5.5 | $0.02713 | $0.02713 |
| Sonnet 5.5 | $0.01356 | $0.01356 |
| Haiku 4.5 | $0.00678 | $0.00678 |
Grade A, and why
secrets-le 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 3d 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.
This is a copy
89% identical to regex-le AGENTS.md — 98 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Secrets-LE
Technical source of truth for this repo. README.md is the user-facing doc; this file is for anyone (human or agent) changing the code.
This repo hosts two products: the extension at the root (this document's scope) and the Rust CLI in crate/ (its own AGENTS.md + SPEC.md). The shared detection corpus lives at crate/signatures/ and crate/fixtures/; scripts/check-detection-parity.ts fails CI when this extension drifts from it.
The Rust CLI also ships a second way, through npm: src/cli/ is its terminal surface rebuilt over this extension's detection engine, bundled to cli/cli.js as the npm package secrets-le. Both install a command named secrets-le, so the npm one is held to the crate's surface byte for byte, which is a different contract from the detection parity above. src/cli/ follows crate/src/cli.rs, scan.rs, walk.rs and mcp/, not the extension's commands: it walks each directory twice, as the crate does, to count what .gitignore and the hidden rule kept out and to name the excluded files whose names say they hold credentials, and it ends the run on a directory it cannot enter. Every finding leaves through utils/mask, the same masking the shared MCP tool uses. scripts/check-cli-parity.ts runs both binaries over one generated tree and fails on any difference in stdout, stderr or exit code, and on any byte of difference in what secrets-le mcp writes. One gap is known and left out of it: the crate's regex engine gives up on a pattern past its backtracking budget and reports the file incomplete, and JavaScript's has no budget, so a document pathological enough to exhaust it is answered by the npm CLI and refused by the crate. scripts/check-cli-pipes.ts, shared with every port, closes stdout or stderr before either binary writes and fails on any difference in what follows, on all three operating systems. A change to the crate's surface changes src/cli/ in the same commit.
What this is
A VS Code extension that scans the workspace for hardcoded secrets (API keys, tokens, passwords, PEM private keys, credentialed database URLs) and can replace detections in the active file with a placeholder. Detection is regex over whole file content — no parser, no network, no writes outside normal document edits.
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.
- 3d ago Changed · +13 lines · +847 tokens per session 6c891c897231
- 7d ago Changed · +54 tokens per session 67d8825b0ede
- 13d ago Changed · +1 lines · +354 tokens per session e1facc27ca59
- 15d ago Changed · -6 lines · -182 tokens per session bfe46761ebc9
- 21d ago Changed · +19 lines · +377 tokens per session 6dc79b08820c
- 1mo ago First seen · 324 lines · 5,332 tokens per session scan A a264a7d89c6f
secrets-le AGENTS.md is an instructions file published in the GitHub repository nolindnaidoo/secrets-le (1 stars, last pushed 3d ago), licensed MIT. It adds 6,782 tokens to every session, about $0.0271 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 89% identical to regex-le AGENTS.md, differing in 98 lines, and is treated as a copy.
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.