Skip to main content
rule CX Codex

pentest-agents-hunting — Claude Code rule: purpose and setup

The pentest-agents-hunting rule structures security hunting around scope, practical impact, and attack chains. It helps an agent drop weak leads and investigate confirmed bugs more deeply.

no license ★ 1,298 updated 2026-06-12

Install into GitHub Copilot · Manually: put the files in place All methods and platforms ↓
.github/instructions/pentest-agents-hunting.instructions.md
Open on GitHub

What pentest-agents-hunting does

The rule applies across the project. Before testing, it directs the agent to read the program’s scope limits and judge whether an attacker could cause real harm without unusual actions from a user. A finding with no practical consequence, such as a standalone open redirect, should be set aside.

Automation is reserved for reconnaissance; hands-on testing is used to investigate vulnerabilities. The rule favors understanding one target in depth, checking sibling API endpoints, and looking for related flaws after confirming an initial bug. It also sets limits on unproductive searches: change direction when progress stalls, and investigate a possible second bug before writing up the first.

Scope matters here. An out-of-scope request can put access at risk. Before reporting exposed data, check whether a visitor can already see it through the web interface; for a leaked API key, test what that credential can access.

What it helps with

  • discard leads with no practical security impact
  • check whether testing stays within the authorized scope
  • inspect related API endpoints for access-control flaws
  • extend a confirmed bug into a higher-impact attack chain
  • verify the permissions granted by a leaked API key

Example prompts for the agent

  • Check this finding against pentest-agents-hunting and assess whether it could cause real harm.
  • Compare my requests with the testing scope and suggest another endpoint to inspect.
  • Look for related endpoints and test whether this vulnerability can form part of an attack chain.

How to install pentest-agents-hunting

Manually: put the files in place

.github/instructions/pentest-agents-hunting.instructions.md

The applyTo field sets which files it applies to

Step by step, with commands for each platform: AGENTS.md vs CLAUDE.md: what they are and which one to use

Questions about pentest-agents-hunting

How do I install pentest-agents-hunting in Claude Code?

Add the rule at .claude/rules/pentest-agents-hunting.md.

What does pentest-agents-hunting do?

It guides security testing toward in-scope findings with practical impact, then encourages deeper checks for related bugs and attack chains.

How does the rule handle a possible data leak?

Check in an incognito session whether the same information is visible in the web interface. For a leaked API key, call the API with that credential and inspect what it can access.

Similar IDE rules

All IDE rules for Security →

From the same set43

The whole set →
sast-gap-analyzer sast-gap-analyzer — a subagent for Claude Code, Cursor and other IDEs that identifies where validation chains break down — missing, insufficient or bypassable checks. Detects bugs between code fragments that each look correct in isolation. CX Codex +1 ★ 1,298repo stars dast-devils-advocate dast-devils-advocate — a skill that catches inflated vulnerabilities in DAST reports. CX Codex +1 ★ 1,298repo stars dast-devils-advocate dast-devils-advocate — an adversarial subagent that questions DAST findings, reruns PoC commands, flags publicly accessible data, and lowers inflated severity ratings before you submit reports. CX Codex +1 ★ 1,298repo stars ssti-hunter ssti-hunter is a Claude Code skill that investigates server-side template injection (SSTI). It activates for user-controlled templates, rule engines, and rendered messages. CX Codex +1 ★ 1,298repo stars ssti-hunter ssti-hunter — a subagent for finding and exploiting Server-Side Template Injection (SSTI) across Jinja2, Twig, Velocity, FreeMarker, ERB, and Handlebars. Maps sandbox blocklists, identifies engine type, and chains bypasses to RCE. CX Codex +1 ★ 1,298repo stars pentest-agents-techniques The pentest-agents-techniques rule guides agents through checks for authorization flaws and data leaks in web apps. Use it when testing systems you’re authorized to assess. CX Codex +1 ★ 1,298repo stars hunt hunt — a prompt for systematic vulnerability detection on target hosts. Reads scope, detects tech stack, auto-selects vuln classes by likelihood, and runs targeted tests with concrete payloads and WAF bypass rules. CX Codex +1 ★ 1,298repo stars hunt Conducts targeted vulnerability hunting by validating scope, fingerprinting stacks, and dispatching exploit tests. CX Codex +1 ★ 1,298repo stars

Project sponsors

Companies that keep this analytics open