m4vic

Bug Hunting — Testing skill for Claude Code

Testing community

Bug bounty hunting & penetration testing skills for Claude, Codex, and any agentic coding tool.

How to install Bug Hunting

This entry records only its repository, not the path inside it, so there is no exact command to give. Open m4vic/bug-hunting and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Bug Hunting does

Bug bounty hunting & penetration testing skills for Claude, Codex, and any agentic coding tool.

Alternatives in Testing

  • Spec Kitty — Spec-Driven Development for serious software developers 1.6k ★
  • Spec Driven Develop — Spec-driven development workflow for AI coding agents: architecture-first planning, task decomposition, GitHub 975 ★
  • Spectra App — Spec-driven development for coding agents — a desktop app, a CLI, and skills for Codex, Claude Code, Cursor, C 735 ★

README

Bug Hunting — bug bounty, penetration testing, AI powered

GitHub stars Version License: MIT GitHub forks

Bug Hunting Skill

**Bug bounty hunting & penetration testing skills for Claude, Codex, and any agentic coding tool.**

A signal-driven, structured skill package that turns a general-purpose coding agent into a disciplined web/API/mobile/cloud/AI-LLM vulnerability hunter — not by dumping a wall of technique text into context, but by routing to only what's relevant, and by making the agent actually *operate* like a hunter (working folders, hypothesis tracking, confirm-before-report), not just recite vuln classes.


What this is

Most "hacking skill" packs for AI agents are a single giant file, or dozens of files, each 300–500+ lines, loaded all at once regardless of relevance — heavy on payout tables and named bug-bounty programs, thin on the actual decision logic a hunter needs mid-recon. That's expensive on tokens and worse, it drowns the model in procedure instead of teaching it how to *think*.

This skill is built the opposite way: a tiny router at the top, six domain-specific signal tables underneath, and 70+ compact technique references that only load when a signal table actually points at them. Nothing loads until it's needed.

What it consists of

bug-hunting/
  SK