By gitdiddy69
Binary reverse engineering with ImHex — Pattern Language, YARA, multi-ISA disassembly. Uses ImHex's native MCP server when installed.
A Claude Code skill suite for offensive and defensive device research. Named for the folklore redcap — a goblin that dips its hat in the blood of its victims. This suite dips its pointer into whichever sibling skill best fits the task.
Use it to:
| Skill | Purpose |
|---|---|
redcap | Meta-dispatcher — routes intent to the right sibling |
redcap-payloads | Offensive payload lookup (PayloadsAllTheThings wrapper) |
redcap-imhex | Binary reverse engineering with ImHex Pattern Language |
redcap-droid | Android APK decompilation + call-flow tracing |
redcap-gpt | Autonomous pentest reasoning (PentestGPT subprocess) |
redcap-kernel | Firmware / kernel analysis workbench |
redcap-compliance | SCAP / STIG / CIS baseline audits |
From Claude Code:
/plugin marketplace add GITDIDDY69/redcap
/plugin install redcap@redcap
/plugin install redcap-payloads@redcap
/plugin install redcap-imhex@redcap
/plugin install redcap-droid@redcap
/plugin install redcap-gpt@redcap
/plugin install redcap-kernel@redcap
/plugin install redcap-compliance@redcap
Install only the siblings you want. The meta-skill (redcap) is useful for discovery; pin it in at minimum.
Most siblings expect a user-local clone of their corresponding upstream fork:
cd ~/Documents/GitHub
gh repo clone GITDIDDY69/PayloadsAllTheThings
gh repo clone GITDIDDY69/ImHex
gh repo clone GITDIDDY69/PentestGPT
gh repo clone GITDIDDY69/linux # large (~4 GB, ADI variant)
gh repo clone GITDIDDY69/content # ComplianceAsCode fork
redcap-payloads → redcap-droid → redcap-kernel → redcap-imhex).This suite is for lawful uses:
You are responsible for ensuring your use complies with applicable laws and terms of service. Unauthorized reverse engineering or network access against systems you do not own or do not have permission to test may violate computer-fraud statutes, terms of service, or regulations.
redcap-droid is adopted from SimoneAvogadro/android-reverse-engineering-skill under Apache 2.0. See NOTICE for full attribution and the list of upstream projects referenced (but not redistributed) by the other siblings.
Apache 2.0 — see LICENSE.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
Autonomous pentest reasoning via PentestGPT CLI. Subprocess wrapper with adversarial-prompt isolation.
Meta-dispatcher for the redcap suite. Routes red-team and device-research intent to the appropriate sibling skill.
Security compliance baseline audit — SCAP, STIG, CIS, PCI-DSS, OSPP. Wraps ComplianceAsCode/content.
Offensive payload library lookup — SQL injection, XSS, SSTI, LDAP, XXE, CSRF, SSRF, deserialization, auth bypass. Wraps a local clone of swisskyrepo/PayloadsAllTheThings.
Firmware and kernel analysis workbench. Unpack partitions, flag-hunt compile-time gates, advertised-vs-actual audit, FCC gap detection.
npx claudepluginhub gitdiddy69/redcap --plugin redcap-imhexBinary reverse engineering, malware analysis, firmware security, and software protection research for authorized security research, CTF competitions, and defensive security
Reverse engineer binaries using Ghidra's headless analyzer. Decompile executables, extract functions, strings, symbols, and analyze call graphs without GUI.
Binary analysis skills for VulHunt MCP - decompilation, dataflow analysis, pattern matching, and more
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Analyze binaries using angr's Python framework. Decompile, recover control flow graphs, find vulnerabilities via symbolic execution, and extract symbols from stripped binaries.
Interact with and understand the DWARF debugging format