←Leaderboard/Security/Claude-BugHunter
Last commit on August 24, 2026·Created on May 5, 2026

elementalsouls/Claude-BugHunter

“An Android red-team pipeline that automates APK acquisition, jadx decompilation, secret grepping, and Frida instrumentation.”
Combined rank
#119
across all skills
In Security
#7
category rank
Stars
5.4k
+1.8% in last 7d
Forks
831
+1.8% in last 7d
Watchers
34
-2.9% in last 7d
Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
TL;DR

Claude-BugHunter provides a technical framework for red-team engagements targeting mobile applications. It streamlines the transition from initial APK acquisition to deep analysis, integrating decompilation and secret extraction into a repeatable workflow.

Security researchers can use these skills to automate the recovery of internal API endpoints, hardcoded JWTs, and pinned certificates while utilizing Frida templates for runtime instrumentation.

WHO IT'S FOR
Bug bounty hunters
orchestrate non-linear vulnerability hunting workflows
Offensive security engineers
execute Android APK red-team pipelines
Application security researchers
hunt for insecure deserialization and RCE
Red team operators
perform infrastructure and identity attack simulations
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.

Use this skill collection

Follow the documented setup, then try a first task.

I’m using

Claude Code on macOS or Linux

Installs: Complete Claude-BugHunter bundle: all 83 skills, 15 slash commands, and the hunt scaffolder, installed into the documented user-level Claude directories. · Claude Code

Before you start
  • Claude Code installed from https://claude.ai/download
  • Python 3.9+ for the cbh CLI runner

Platform: macOS or Linux

Run from: ~/security-research/Claude-BugHunter

  1. In a terminal, create and enter the documented checkout parent directory.

    mkdir -p ~/security-research && cd ~/security-research
  2. In the same terminal, clone the repository and enter it.

    git clone https://github.com/elementalsouls/Claude-BugHunter.git
    cd Claude-BugHunter
  3. From the repository directory, run the installer in the terminal. Existing same-named skills are backed up outside the skills and commands directories.

    bash scripts/install.sh
INSTALL.md ↗ · Checked Nov 5, 2026

Give it something to do.

Suggested first task

Check ownership before testing recon findings

Uses recon-scope-triage

  • A small batch of ASM, recon, or OSINT findings
  • The target's confirmed domains, organization identifiers, and authorized scope
  • Available ownership evidence for the listed assets
Use recon-scope-triage to review a small batch from my supplied recon export against the target's confirmed domains and organization identifiers. For each asset, identify concrete ownership evidence, flag unrelated same-name matches, and list anything that needs verification before testing. Work only from the supplied material.
INSTALL.md ↗ · Checked Nov 5, 2026skills/recon-scope-triage/SKILL.md ↗ · Checked Nov 5, 2026
Suggested first task

Assess one captured redirect finding

Uses hunt-open-redirect

  • One candidate URL from an authorized target
  • Captured response headers or browser redirect evidence
  • The controlled destination domain and any existing chain evidence
Use hunt-open-redirect to review one candidate URL and its captured response or browser evidence. Identify the redirect parameter, assess whether the evidence shows navigation to my controlled domain, and distinguish a standalone redirect from any demonstrated chain. Explain what remains unverified without making new requests or attempting account takeover.
skills/hunt-open-redirect/SKILL.md ↗ · Checked Nov 5, 2026INSTALL.md ↗ · Checked Nov 5, 2026
Suggested first task

Draft one client-facing red-team finding

Uses redteam-report-template

  • One confirmed finding from an authorized external enterprise red-team engagement
  • Observed facts, technical explanation, impact, remediation information, and PoC evidence
  • Available severity, status, CVSS score/vector, affected asset, and client formatting requirements
Use redteam-report-template to draft one finding for my external enterprise red-team client from the supplied confirmed evidence. Use Subject, Observations, Description, Impact, Recommendation, and PoC sections. Keep observations factual and the subject in plain English; include supplied severity, status, CVSS, and affected-asset details, and mark missing information rather than inventing it. Return a draft for review without sending or publishing it.
INSTALL.md ↗ · Checked Nov 5, 2026skills/redteam-report-template/SKILL.md ↗ · Checked Nov 5, 2026