Borrowing it
Nothing to install: this file belongs to n-shadloo/secure-code-auditor. 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/n-shadloo/secure-code-auditor/main/AGENTS.mdgit clone --depth 1 https://github.com/n-shadloo/secure-code-auditorWrote 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/n-shadloo/secure-code-auditor/agents-md)<a href="https://agentmods.dev/instructions/n-shadloo/secure-code-auditor/agents-md"><img src="https://agentmods.dev/badge/instructions/n-shadloo/secure-code-auditor/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/n-shadloo/secure-code-auditor/agents-md"><img src="https://agentmods.dev/badge/instructions/n-shadloo/secure-code-auditor/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.01063 | $0.01063 |
| Opus 5.5 | $0.00425 | $0.00425 |
| Sonnet 5.5 | $0.00213 | $0.00213 |
| Haiku 4.5 | $0.00106 | $0.00106 |
Grade A, and why
secure-code-auditor 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 — 86 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This repository is a backend security skill. The canonical instructions live
in SKILL.md, which routes to the topic files under references/. An agent
that works in this repository loads SKILL.md first. Then it reads only the
references/*.md file(s) relevant to the task.
The primary integration is Claude (Anthropic Agent Skills). This file and
its siblings let other agents use the same content. They are pointers, not
copies. Where anything here disagrees with SKILL.md, SKILL.md wins.
Self-improvement
If this skill's text or script caused a mistake, or you had to find a step
yourself, record it at once. Before you claim the task is done, end the report
with Skill defects:. Section 0 of SELF-IMPROVEMENT.md gives the rules. If
~/.skill-improvements/secure-code-auditor/ exists, do section 3 first.
What this skill does
It reviews backend code for security issues, and it applies secure defaults while code is written. The corpus sits on the OWASP Top 10:2025 spine, with the API Security Top 10:2023 and ASVS 5.0 beside it. Each reference carries a stack-neutral principle layer and a deep Django and DRF layer. Every control is stated in a review form and a write-time form together.
The coverage spans the whole backend. It runs from the audit workflow and the
entry-point inventory, through access control, authentication, injection,
integrity, cryptography, and configuration. It reaches the API surfaces that
are not DRF routes. It covers the database and data-lifecycle layers,
service identity, deployment, file uploads, and agent and MCP tool surfaces.
It also covers the auditing agent's own access. The SKILL.md router names
each file's exact surface, so do not duplicate that list here.
Two modes
- Review-time. Audit existing code, and produce prioritized findings.
Each finding carries a severity, a location, a CWE and OWASP mapping, the
confirmed source-to-sink path with the protection that failed, and a fix.
The codebase stays read-only. Load
references/01-audit-workflow.mdbefore any topic file. It owns the sweep, and the topic files answer the questions the sweep generates. The report ends with what was not reviewed. - Write-time. Apply the standing secure-default contract while you generate code. Where a default conflicts with the request, apply the default and say so in one line. Close with a short security-decisions note rather than a findings report. The rule for each generation moment sits beside the control it completes, in the reference the router names.
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 · -3 tokens per session aed007ff787f
- 19d ago Changed · +7 tokens per session 3d15a6b9a1e4
- 1mo ago Changed · +5 lines · +63 tokens per session 15fd9f1c712f
- 1mo ago First seen · 81 lines · 996 tokens per session scan A 34528572ed41
secure-code-auditor AGENTS.md is an instructions file published in the GitHub repository n-shadloo/secure-code-auditor (4 stars, last pushed 4d ago), licensed MIT. It adds 1,063 tokens to every session, about $0.0043 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.