Borrowing it
Nothing to install: this file belongs to bhuvangupta/vapt-claude. 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/bhuvangupta/vapt-claude/main/AGENTS.mdgit clone --depth 1 https://github.com/bhuvangupta/vapt-claudeWrote 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/bhuvangupta/vapt-claude/agents-md)<a href="https://agentmods.dev/instructions/bhuvangupta/vapt-claude/agents-md"><img src="https://agentmods.dev/badge/instructions/bhuvangupta/vapt-claude/agents-md.svg" alt="Measured on agentmods" 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.00683 | $0.00683 |
| Opus 5 | $0.00342 | $0.00342 |
| Sonnet 5 | $0.00137 | $0.00137 |
| Haiku 4.5 | $0.00068 | $0.00068 |
Grade A, and why
vapt-claude AGENTS.md scanned grade A with 1 finding 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 7d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| `WebFetch` | `shell` with `curl` | Copies of this mod
1 near-identical copy found in the catalogue:
- vapt-claude GEMINI.md — 91% identical, 22 lines differ
How it starts
The opening of the file, as written. The whole thing — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VAPT — Web Application Penetration Testing (Codex CLI)
This project provides a full-spectrum VAPT (Vulnerability Assessment and Penetration Testing) skill suite. While originally built for Claude Code, the testing methodology and skill files work with Codex CLI.
How to Use
Instead of /vapt <command>, use natural language:
vapt audit https://example.com
vapt recon https://example.com
vapt ssl https://example.com
Tool Mapping
The skill files reference Claude Code tool names. In Codex CLI, use these equivalents:
| Claude Code Tool | Codex Equivalent |
|---|---|
Bash |
shell |
Read |
read_file |
Write |
write_file |
Edit |
patch |
Glob |
shell with find |
Grep |
shell with grep / rg |
WebFetch |
shell with curl |
Agent (subagent) |
Run tasks sequentially |
Skill Files
All testing methodology lives in the skills/ directory. Each SKILL.md file contains:
- What to test and how
- Which security tools to use (with fallbacks)
- Output format and findings structure
Read the relevant skill file before starting a test:
vapt/SKILL.md— Main orchestrator and full audit flowskills/vapt-recon/SKILL.md— Reconnaissance & OSINTskills/vapt-network/SKILL.md— Network & port scanningskills/vapt-ssl/SKILL.md— SSL/TLS & cryptographyskills/vapt-scan/SKILL.md— Web application scanningskills/vapt-inject/SKILL.md— Injection testing (SQLi, XSS, SSTI)skills/vapt-auth/SKILL.md— Authentication & session testingskills/vapt-authz/SKILL.md— Authorization & access controlskills/vapt-api/SKILL.md— API security testingskills/vapt-graphql/SKILL.md— GraphQL security testingskills/vapt-websocket/SKILL.md— WebSocket security testingskills/vapt-cloud/SKILL.md— Cloud misconfiguration testingskills/vapt-headers/SKILL.md— Security headers & infrastructureskills/vapt-logic/SKILL.md— Business logic testingskills/vapt-report/SKILL.md— Markdown report generationskills/vapt-report-pdf/SKILL.md— PDF report generation
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.
- 7d ago First seen · 64 lines · 683 tokens per session scan A d8e34803fca8
vapt-claude AGENTS.md is an instructions file published in the GitHub repository bhuvangupta/vapt-claude (1 stars, last pushed 5mo ago), licensed MIT. It adds 683 tokens to every session, about $0.0034 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). 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).
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.
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.