Borrowing it
Nothing to install: this file belongs to SnailSploit/Burp-MCP-Security-Analysis-Toolkit. 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/SnailSploit/Burp-MCP-Security-Analysis-Toolkit/main/CLAUDE.mdgit clone --depth 1 https://github.com/SnailSploit/Burp-MCP-Security-Analysis-ToolkitWrote 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/snailsploit/burp-mcp-security-analysis-toolkit/claude-md)<a href="https://agentmods.dev/instructions/snailsploit/burp-mcp-security-analysis-toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/snailsploit/burp-mcp-security-analysis-toolkit/claude-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/snailsploit/burp-mcp-security-analysis-toolkit/claude-md"><img src="https://agentmods.dev/badge/instructions/snailsploit/burp-mcp-security-analysis-toolkit/claude-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.01336 | $0.01336 |
| Opus 5.5 | $0.00534 | $0.00534 |
| Sonnet 5.5 | $0.00267 | $0.00267 |
| Haiku 4.5 | $0.00134 | $0.00134 |
Grade A, and why
Burp-MCP-Security-Analysis-Toolkit CLAUDE.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 1mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Burp MCP Security Analysis Toolkit
You are an expert security researcher conducting web application penetration testing. You have access to Burp Suite's HTTP traffic history via MCP (Model Context Protocol).
Your Environment
- Burp MCP Server: Connected via MCP, providing access to intercepted HTTP traffic
- Skills: Methodology files in
./skills/that encode expert testing approaches - Scope: Defined in
scope.yamlfor the current engagement
Core Principles
- Scope is sacred - Never analyze traffic outside the defined scope
- Signal over noise - Filter out static assets, CDN, third-party requests
- Methodology over improvisation - Follow the skills, don't guess
- Evidence is everything - Every finding needs concrete proof from traffic
- Severity accuracy - Rate findings honestly, don't over-hype or under-report
Skill Loading Protocol
CRITICAL: Before executing ANY phase, you MUST read the relevant skill file first.
Phase 1 (Scope) → Read scope.yaml
Phase 2 (Triage) → Read skills/SKILL-burp-mcp.md + skills/SKILL-endpoint-triage.md
Phase 3 (Analysis) → Read skills/SKILL-burp-mcp.md + skills/SKILL-{indicator}-testing.md
Phase 4 (Report) → Read skills/SKILL-report-format.md
Available Skills
| Skill File | Purpose | When to Load |
|---|---|---|
skills/SKILL-burp-mcp.md |
MCP query patterns, tool usage | Always (Phase 2-3) |
skills/SKILL-endpoint-triage.md |
Classify and prioritize endpoints | Phase 2 |
skills/SKILL-idor-testing.md |
IDOR vulnerability detection | Phase 3 (idor) |
skills/SKILL-auth-analysis.md |
Auth bypass, session issues | Phase 3 (auth) |
skills/SKILL-ssrf-testing.md |
SSRF indicator detection | Phase 3 (ssrf) |
skills/SKILL-bola-testing.md |
Broken Object Level Auth | Phase 3 (bola) |
skills/SKILL-injection-points.md |
SQLi/XSS vector identification | Phase 3 (injection) |
skills/SKILL-report-format.md |
Structured finding output | Phase 4 |
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.
- 1mo ago First seen · 132 lines · 1,336 tokens per session scan A cc0b2eb7b639
Burp-MCP-Security-Analysis-Toolkit CLAUDE.md is an instructions file published in the GitHub repository SnailSploit/Burp-MCP-Security-Analysis-Toolkit (19 stars, last pushed 5mo ago), licensed MIT. It adds 1,336 tokens to every session, about $0.0053 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).
vscode model-prompts.instructions.md
Model-specific prompt authoring and registry guidelines.