Borrowing it
Nothing to install: this file belongs to xsourabhsharma/ai-security-audit-pro. 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/xsourabhsharma/ai-security-audit-pro/main/AGENTS.mdgit clone --depth 1 https://github.com/xsourabhsharma/ai-security-audit-proWrote 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/xsourabhsharma/ai-security-audit-pro/agents-md)<a href="https://agentmods.dev/instructions/xsourabhsharma/ai-security-audit-pro/agents-md"><img src="https://agentmods.dev/badge/instructions/xsourabhsharma/ai-security-audit-pro/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/xsourabhsharma/ai-security-audit-pro/agents-md"><img src="https://agentmods.dev/badge/instructions/xsourabhsharma/ai-security-audit-pro/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.00350 | $0.00350 |
| Opus 5 | $0.00175 | $0.00175 |
| Sonnet 5 | $0.00070 | $0.00070 |
| Haiku 4.5 | $0.00035 | $0.00035 |
Grade A, and why
ai-security-audit-pro 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 10d 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
Agent Instructions
Security Audit Pro is a defensive security audit toolkit. Use it when the user asks to find bugs, security vulnerabilities, OWASP issues, exposed secrets, dependency vulnerabilities, weak headers, API risks, or website weaknesses.
Core Workflow
- Confirm scope and authorization before active testing of hosted or third-party targets.
- Prefer local source, configs, lockfiles, and logs before live probing.
- Run the CLI from this repository root:
node scripts/security-audit.mjs --target <path-or-url> --mode passive --out security-audit-report.md
- For authorized URL targets, use:
node scripts/security-audit.mjs --target <url> --mode standard --authorized --out report.md --html-out report.html
- For authorized deep non-destructive scans, use:
node scripts/security-audit.mjs --target <url> --mode active --profile deep --authorized --scope-file templates/authenticated-audit-scope.md --out report.md --html-out report.html --pdf-out report.pdf
Boundaries
- Never print secrets. Redact tokens, cookies, API keys, passwords, and private configuration.
- Do not run destructive exploits, credential attacks, denial of service, persistence, stealth, or data dumping.
- Mark scanner-only or client-side-only claims as
Needs validationuntil server-side behavior is confirmed. - Always report skipped checks and residual risk.
Report Standard
Lead with confirmed high-impact findings. Every finding should include severity, status, affected surface, evidence, risk, impact, OWASP/CWE mapping when applicable, remediation, and safe validation steps.
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.
- 10d ago First seen · 37 lines · 350 tokens per session scan A 3c9a175a26ff
ai-security-audit-pro AGENTS.md is an instructions file published in the GitHub repository xsourabhsharma/ai-security-audit-pro (4 stars, last pushed 2mo ago), licensed MIT. It adds 350 tokens to every session, about $0.0018 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.
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.
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).
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.