Claude Code bug bounty agent. Install in current workspace: npx -y hacker-bob-cc@latest install "$PWD" then restart C...
Copy the install, test the workflow, then decide if it earns a permanent slot.
The signal is softer here. Treat it like a pattern source unless it solves a very specific gap.
Copy the install, test the workflow, then decide if it earns a permanent slot.
You can test this quickly and remove it cleanly if it misses.
GitHub health 100/100. no security policy. Fresh enough repo health and manageable issue load keep the risk controlled.
AI Agent
Claude Code
Model
Claude
Fastest way to find out if hacker-bob belongs in your setup.
Copy the install command, run a real test, and back it out cleanly if it slows you down.
git clone https://github.com/vmihalis/hacker-bob ~/.claude/skills/hacker-bobRun this first. You will know quickly if the workflow earns a permanent slot.
rm -rf ~/.claude/skills/hacker-bobNo messy cleanup loop. If it misses, remove it and keep moving.
Install Location
~/ └─ .claude/ ├─ commands/ ├─ skills/ │ └─ hacker-bob/ ← installs here ├─ agents/ └─ settings.json
Claude Code bug bounty agent. Install in current workspace: npx -y hacker-bob-cc@latest install "$PWD" then restart Claude and run /bob-hunt target.com
Source: GitHub repository
Source check: July 18, 2026
Upstream commit: July 18, 2026
Repository state: Not marked archived
Honeystax upvotes are community interest signals, not star ratings. GitHub stars and repository health are source measurements; editorial risk and trial-cost notes are Honeystax analysis.