New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Operate Binary Analysis Toolchain

by cyberful in cyberful/cyberful

Operate Ghidra headless analysis, radare2, platform binary utilities, decompilers, and targeted dynamic evidence for advanced native and bytecode security review.

AGPL-3.0Auto-check passedSecurity

Install Operate Binary Analysis Toolchain

skills CLI
$ npx skills add cyberful/cyberful --skill operate-binary-analysis-toolchain -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install cyberful/cyberful operate-binary-analysis-toolchain --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/cyberful/cyberful.git skills-src && mkdir -p .claude/skills && cp -r skills-src/cyberful/builtin/skills/operate-binary-analysis-toolchain .claude/skills/operate-binary-analysis-toolchain && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
operate-binary-analysis-toolchain
GitHub stars
135
Token cost
~1.2k tokens
SKILL.md length
493 words
Files
3 (incl. references)
Skills in repo
85
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Operate Ghidra headless analysis, radare2, platform binary utilities, decompilers, and targeted dynamic evidence for advanced native and bytecode security review.

  • Works in 6 steps: call ghidra_import with a relative… → poll the returned identifier with… → use ghidra_search, ghidra_xrefs, and… → …
  • Optimized binary triage
  • SKILL.md covers Establish artifact identity, Triage before decompiling, Reconstruct security invariants and Account for compiler…, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Operate Binary Analysis Toolchain is an agent skill from cyberful/cyberful. Operate Ghidra headless analysis, radare2, platform binary utilities, decompilers, and targeted dynamic evidence for advanced native and bytecode security review. Use for stripped or optimized binary triage, architecture and hardening analysis, call-graph and dataflow reconstruction, patch diffing, parser or trust-boundary review, JNI/native correlation, or resolving disagreements between decompilers and actual machine behavior.

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/binary-analysis-fieldbook.md`).

It sits in Security, covering Reverse engineering and malware. It works with Ghidra. The repository describes itself as: Cyberful is an open-source AI Red Team for discovering, exploiting, verifying, and remediating vulnerabilities. The licence is AGPL-3.0.

When your agent uses it

  • Optimized binary triage
  • Architecture and hardening analysis
  • Call-graph and dataflow reconstruction
  • Trust-boundary review

Example prompts

  • “/operate-binary-analysis-toolchain”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. call ghidra_import with a relative workarea path and retain its SHA-256;
  2. poll the returned identifier with ghidra_job instead of blocking on analysis;
  3. use ghidra_search, ghidra_xrefs, and ghidra_call_graph to narrow the boundary; when a name or signature is ambiguous, select only a…
  4. confirm decisive sites with ghidra_listing and ghidra_decompile;
  5. preserve hypotheses and confidence with ghidra_annotations;
  6. create a ghidra_project checkpoint before handoff.

What it can do on your machine

Read from SKILL.md and the folder at commit ec598a6. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Operate Binary Analysis Toolchain loads about 1.2k tokens when it runs, and up to ~1.9k if it reads all its reference files. Until then it costs about 117 tokens; SKILL.md has 493 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~117
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from cyberful/cyberful at commit ec598a6, republished under its AGPL-3.0 licence (© cyberful). 493 words, ~1,245 tokens.

Download SKILL.mdSave it as .claude/skills/operate-binary-analysis-toolchain/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
operate-binary-analysis-toolchain
description
Operate Ghidra headless analysis, radare2, platform binary utilities, decompilers, and targeted dynamic evidence for advanced native and bytecode security review. Use for stripped or optimized binary triage, architecture and hardening analysis, call-graph and dataflow reconstruction, patch diffing, parser or trust-boundary review, JNI/native correlation, or resolving disagreements between decompilers and actual machine behavior.
metadata.domain
security-tooling
metadata.subdomain
binary-analysis
metadata.triggers
reverse engineer binary, inspect executable, analyze disassembly, inspect binary mitigations, decompile native code, assess exploit primitives
metadata.tags
Ghidra, radare2, ELF, PE, Mach-O, reverse-engineering

Operate Binary Analysis Toolchain

Treat decompiler output as a lossy hypothesis. Anchor conclusions in bytes, relocations, calling convention, control/data flow, and runtime evidence.

Establish artifact identity

Record cryptographic hash, source/provenance, format, architecture/subarchitecture, endianness, ABI, load address, sections/segments, imports/exports, relocations, interpreter/runtime, signatures, debug symbols, packing, and hardening. Use bounded xxd views when raw bytes resolve format ambiguity, and archive_extract for signature-detected, bounded, atomic ZIP, TAR-family, compressed-stream, and native 7-Zip publication. Keep universal/fat slices and platform variants separate.

Triage before decompiling

Map entry points, initialization/finalization, exported interfaces, IPC/network/file/parser boundaries, privilege transitions, cryptographic and verification APIs, dynamic loading, dangerous memory/process functions, error/log paths, and embedded configuration. Use strings only as cross-reference seeds.

Use the persistent Ghidra MCP as the primary semantic workspace:

  1. call ghidra_import with a relative workarea path and retain its SHA-256;
  2. poll the returned identifier with ghidra_job instead of blocking on analysis;
  3. use ghidra_search, ghidra_xrefs, and ghidra_call_graph to narrow the boundary; when a name or signature is ambiguous, select only a returned canonical address rather than guessing;
  4. confirm decisive sites with ghidra_listing and ghidra_decompile;
  5. preserve hypotheses and confidence with ghidra_annotations;
  6. create a ghidra_project checkpoint before handoff.

The project, analysis, names, comments, bookmarks, and job history survive phase and runtime replacement. Cite the automatically captured raw/ghidra/ evidence paths in handoffs and reports. Never request arbitrary scripts or binary patching through the MCP; use radare2 and platform tools to independently confirm sections, functions, references, and instructions at critical sites.

Read references/binary-analysis-fieldbook.md when reconstructing optimized code or patch-diffing.

Reconstruct security invariants

For each boundary:

  1. identify exact calling convention and argument ownership;
  2. trace length, signedness, encoding, lifetime, and error values;
  3. locate all dominating validation and authorization branches;
  4. follow indirect calls, vtables, jump tables, callbacks, and dynamic imports;
  5. inspect cleanup and exceptional exits;
  6. verify ambiguous behavior in disassembly or a bounded runtime trace.

Search both forward from untrusted input and backward from sensitive effects.

Show full SKILL.md (173 more words)Show less

Account for compiler transformations

Expect inlining, tail calls, thunks, split functions, merged constants, stack-slot reuse, dead-code elimination, exception tables, link-time optimization, and control-flow flattening. Rename functions and types only with confidence annotations. Preserve raw addresses and image bases so another analyst can reproduce references.

Diff by semantics

For patches, normalize addresses and compiler noise; compare control-flow shape, constants, call targets, bounds, validation order, error handling, and data structure layout. Trace the changed invariant outward to sibling functions and older product branches. A one-line source fix may compile into several sites, while a large binary diff may be toolchain noise.

Use binary_diff compare_programs, changed_functions, changed_calls, and changed_constants to retain reproducible first-pass evidence. Use security_candidates only to prioritize manual validation; its heuristic label is not a finding. Confirm decisive changes in Ghidra listings or raw disassembly.

Deliver

Preserve hashes, loader options, analysis database/project, script versions, architecture assumptions, annotated functions, raw disassembly at decisive sites, xrefs, dynamic traces, unresolved indirect calls, and confidence. Report the earliest violated invariant and a reproducible input or state when possible.

© cyberful, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 2 other files (references) in cyberful/builtin/skills/operate-binary-analysis-toolchain of cyberful/cyberful.

  • SKILL.md
  • agents/openai.yaml
  • references/binary-analysis-fieldbook.md

Open the folder on GitHubat commit ec598a6

Compare with similar skills

Operate Binary Analysis Toolchain next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Operate Binary Analysis Toolchain compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Operate Binary Analysis Toolchain this skillcyberful/cyberful135—~1.2kAutomated safety check: PassAGPL-3.0
Ghidra ReOrbitCurve/firmware-reverse-engineering214—~4.2kAutomated safety check: PassApache-2.0
Firmware Security ReportsOrbitCurve/firmware-reverse-engineering214—~4.1kAutomated safety check: PassApache-2.0
Bench ExperimentDavidClawson/OpenScope-2C53T116—~1kAutomated safety check: PassGPL-3.0
Go Rust Reversezhaoxuya520/reverse-skill40k2 repos~339Automated safety check: PassMIT
Reverse Engineering Signaturesvillith/relink-logs157—~7.5kAutomated safety check: PassMIT

Similar skills

  • Ghidra Re

    OrbitCurve/firmware-reverse-engineering

    Expert-level Ghidra reverse engineering for firmware binaries with emphasis on stripped binary analysis, automated function discovery, cryptographic routine identification, authentication logic…

    214 GitHub stars~4.2k tokensUpdated 1 mo ago
    SecurityAuto-check passed

  • Firmware Security Reports

    OrbitCurve/firmware-reverse-engineering

    Evidence-based security report generation for firmware assessments.

    214 GitHub stars~4.1k tokensUpdated 1 mo ago
    SecurityAuto-check passed

  • Bench Experiment

    DavidClawson/OpenScope-2C53T

    Run and record a hardware experiment on the 2C53T bench using a controlled five-step cycle.

    116 GitHub stars~1k tokensUpdated today
    SecurityAuto-check passed

  • Go Rust Reverse

    zhaoxuya520/reverse-skill

    A skill your agent uses for reverse engineering stripped Go and Rust binaries including runtime recognition, pclntab/moduel data recovery, panic strings, and idiomatic decompilation recovery.

    40k GitHub starsUsed in 2 repos~339 tokens
    SecurityAuto-check passed

  • Reverse Engineering Signatures

    villith/relink-logs

    A skill your agent uses when a Granblue Fantasy Relink game patch breaks the GBFR Logs hook — signatures no longer match, "Could not find match for pattern" / "Could not find <offset" warnings…

    157 GitHub stars~7.5k tokensUpdated 12 days ago
    SecurityAuto-check passed

  • Analyzing Packed Malware With Upx Unpacker

    mukul975/Anthropic-Cybersecurity-Skills

    Identifies and unpacks UPX-packed malware samples, including binaries with modified UPX magic bytes or headers that block automated decompression, to recover the original executable for static…

    34k GitHub stars~3k tokensUpdated 1 mo ago
    SecurityAuto-check passed

More from cyberful/cyberful

All 85 skills in this repo

  • Audit Infrastructure As Code

    cyberful/cyberful

    Audit infrastructure-as-code artifacts for unsafe defaults, policy gaps, privilege exposure, control drift, and deployment-impact evidence.

    135 GitHub stars~649 tokensUpdated 1 mo ago
    Auto-check passed

  • Audit Kubernetes Policy Enforcement

    cyberful/cyberful

    Audit Kubernetes admission and policy-as-code enforcement against local workload manifests, exception paths, namespace scope, and deployment evidence.

    135 GitHub stars~610 tokensUpdated 1 mo ago
    Auto-check passed

  • Audit Pci Dss Penetration Test Evidence

    cyberful/cyberful

    Audit PCI DSS penetration-test methodology, scope, internal and external reports, segmentation results, tester independence, remediation, retesting, retention, and multi-tenant support evidence.

    135 GitHub stars~1k tokensUpdated 1 mo ago
    Auto-check passed

  • Operate Content Discovery

    cyberful/cyberful

    Design and interpret advanced content discovery with ffuf and complementary web fuzzers.

    135 GitHub stars~1.5k tokensUpdated 1 mo ago
    Auto-check passed

  • Operate Network Recon

    cyberful/cyberful

    Build a high-fidelity network and service inventory using Nmap, Masscan, packet capture, DNS, and protocol-specific follow-up.

    135 GitHub stars~1.1k tokensUpdated 1 mo ago
    Auto-check passed

  • Operate Sast Toolchain

    cyberful/cyberful

    Operate Semgrep and source-oriented static analysis as a hypothesis, coverage, and regression system during advanced code audits.

    135 GitHub stars~1.3k tokensUpdated 1 mo ago
    Auto-check passed

Works with

Categories

Questions about Operate Binary Analysis Toolchain

What does Operate Binary Analysis Toolchain do?

Operate Ghidra headless analysis, radare2, platform binary utilities, decompilers, and targeted dynamic evidence for advanced native and bytecode security review. Operate Binary Analysis Toolchain is an agent skill from cyberful/cyberful. Operate Ghidra headless analysis, radare2, platform binary utilities, decompilers, and targeted dynamic evidence for advanced native and bytecode security review.

When should I use Operate Binary Analysis Toolchain?

Operate Binary Analysis Toolchain fits situations like: optimized binary triage; architecture and hardening analysis; call-graph and dataflow reconstruction; trust-boundary review.

How do I install Operate Binary Analysis Toolchain in Claude Code?

Run `npx skills add cyberful/cyberful --skill operate-binary-analysis-toolchain -a claude-code`. Or copy the skill folder (cyberful/builtin/skills/operate-binary-analysis-toolchain in cyberful/cyberful) into .claude/skills/operate-binary-analysis-toolchain in your project. Claude Code loads it when a task matches its description.

How do I install Operate Binary Analysis Toolchain in Codex?

Run `npx skills add cyberful/cyberful --skill operate-binary-analysis-toolchain -a codex`. Or copy the skill folder (cyberful/builtin/skills/operate-binary-analysis-toolchain in cyberful/cyberful) into .agents/skills/operate-binary-analysis-toolchain in your project. Codex loads it when a task matches its description.

Can I use Operate Binary Analysis Toolchain in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cyberful/cyberful --skill operate-binary-analysis-toolchain -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/operate-binary-analysis-toolchain, .gemini/skills/operate-binary-analysis-toolchain, .github/skills/operate-binary-analysis-toolchain and .opencode/skills/operate-binary-analysis-toolchain in your project.

What does Operate Binary Analysis Toolchain need to run?

SKILL.md names no scripts, command-line tools or credentials: Operate Binary Analysis Toolchain is instructions for the agent only.

Does Operate Binary Analysis Toolchain access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Operate Binary Analysis Toolchain safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Operate Binary Analysis Toolchain use?

Operate Binary Analysis Toolchain is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Operate Binary Analysis Toolchain use?

About 1.2k tokens (SKILL.md is roughly 5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 644 tokens, read only when the agent opens those files.

What are the alternatives to Operate Binary Analysis Toolchain?

Skills that share tags, products or a category with Operate Binary Analysis Toolchain: Ghidra Re (OrbitCurve/firmware-reverse-engineering, 214 stars), Firmware Security Reports (OrbitCurve/firmware-reverse-engineering, 214 stars), Bench Experiment (DavidClawson/OpenScope-2C53T, 116 stars) and Go Rust Reverse (zhaoxuya520/reverse-skill, 40k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Operate Binary Analysis Toolchain?

cyberful (a GitHub organization) maintains it in cyberful/cyberful, which has 135 GitHub stars. The repository holds 85 skills in this directory. The repository was last updated on August 24, 2026.

Source: cyberful/cyberful on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.