pentest-agents-mistakes — Claude Code rule: testing pitfalls
pentest-agents-mistakes is a rule that collects 11 mistakes agents make in security testing, from hallucinated paths to fake PoCs. Read it before a vulnerability hunt.
no license ★ 1,298 updated 2026-06-12
.github/instructions/pentest-agents-mistakes.instructions.mdWhat pentest-agents-mistakes does
This is a registry of real failures. Each rule came from a session where an agent wasted time, got corrected, or shipped a weak finding. The top 11 cover the essentials: save artifacts to disk, never invent file paths, validate before reporting, use a real browser for WAF and JavaScript checks, prove impact with actual data not theory, test sibling endpoints and fields, match CVSS version to the platform, read policy before the first request, only call a finding CONFIRMED when you have a working PoC on the live target, recalibrate after correction.
One rule stops a common trap: satisfying gate checkers with markers instead of evidence. If writing a string clears a gate but no real work happens, the gate fails. Other rules flag sneakier problems: re-asking for credentials or tokens that are already in session memory, listing findings when asked to rank them, using placeholder usernames like researcher when the real identity is in policy.md.
What it helps with
- Distinguish a real proof of impact from a fingerprint or chain of inference
- Keep findings persisted so the next session doesn't re-discover everything
- Pick the right CVSS scoring system for each bug bounty platform
- Break the pattern when the same mistake repeats
- Stop agents from gaming checklists with fake markers instead of work
Example prompts for the agent
- Read pentest-agents-mistakes at the start of
/hunton a new scope - If an agent repeats the same mistake twice, point it to the relevant rule
- Verify credentials and test accounts are loaded into session memory before kicking off a recon phase
How to install pentest-agents-mistakes
Manually: put the files in place
.github/instructions/pentest-agents-mistakes.instructions.mdThe applyTo field sets which files it applies to
Manually: put the files in place
.claude/rules/pentest-agents-mistakes.mdThe paths frontmatter field limits the files: move applyTo from the source into paths
AGENTS.md
Codex reads AGENTS.md: paste the rule text there
Manually: put the files in place
.cursor/rules/pentest-agents-mistakes.mdcFrontmatter: description, globs, alwaysApply. Move applyTo from the source into globs, or the rule will not attach on its own
Manually: put the files in place
.devin/rules/pentest-agents-mistakes.mdManually: put the files in place
.clinerules/pentest-agents-mistakes.mdStep by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use
Questions about pentest-agents-mistakes
How do I install pentest-agents-mistakes in Claude Code?
Copy the file .claude/rules/pentest-agents-mistakes.md from the repository into your local .claude/rules/ folder. Claude Code will load the rule automatically in the next session.
What is pentest-agents-mistakes?
A collection of 11 behavioral rules for agents hunting bugs in web applications and APIs. Each rule documents a real failure and how to avoid it.
Why does CVSS version matter when choosing a bounty platform?
HackerOne requires CVSS 3.1, while Bugcrowd, Intigriti, and Immunefi use CVSS 4.0. Submitting the wrong version forces a triage rework and delays payment.