This is for when you're actually submitting bounty reports, not running a general security audit. It filters out the noise that platforms reject anyway: local-only deserialization, hardcoded shell commands, self-XSS, test files. Instead it focuses on remotely reachable paths like SSRF, auth bypass, SQL injection, and command injection where you can prove user input hits a dangerous sink. The workflow is practical: check scope first, find real entrypoints, trace the code path end to end, then build a minimal PoC. It includes a quality gate checklist and report template so you're not wasting time on duplicates or out-of-scope findings. Use this when the question is "will this pay?" not "is this theoretically unsafe?"
npx -y skills add affaan-m/everything-claude-code --skill security-bounty-hunter --agent claude-codeInstalls into .claude/skills of the current project.
Select a file.
hoodini/ai-agents-skills
addyosmani/agent-skills
giuseppe-trisciuoglio/developer-kit
agamm/claude-code-owasp