agentsclimarketplace

Headless ghidra intake

Skill ByteLandTechnology/headless-ghidra/headless-ghidra-intake

Headless Ghidra reverse-engineering skill family for reproducible, evidence-backed workflows and audit-ready Markdown outputs.

Install
npx -y skills add ByteLandTechnology/headless-ghidra --skill headless-ghidra-intake

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

P0 phase skill for Headless Ghidra intake. Use when a target binary/archive needs identity confirmation, workspace initialization, Ghidra discovery, binary inspection, or analysis scope setup before any Ghidra analysis runs.

SKILL.md

2.0 KB, 439 tokens by cl100k_base, as published. Nobody here has run it

Headless Ghidra Intake — P0

P0 prepares a target for the rest of the workflow. It is responsible for turning an input binary or archive path into a valid ghidra-agent-cli workspace target and recording the initial analysis scope.

Required ghidra-agent-cli Commands

  • ghidra-agent-cli workspace init
  • ghidra-agent-cli ghidra discover
  • ghidra-agent-cli inspect binary
  • ghidra-agent-cli scope show
  • ghidra-agent-cli scope set
  • ghidra-agent-cli scope add-entry
  • ghidra-agent-cli scope remove-entry
  • ghidra-agent-cli gate check --phase P0

Archive normalization and any target-specific bootstrap scripts may still run as backend details until the CLI exposes them directly.

Inputs

  • User-provided binary or archive path
  • Workspace root
  • Local environment needed for Ghidra discovery

Outputs

  • targets/<target-id>/ghidra-projects/
  • artifacts/<target-id>/pipeline-state.yaml
  • artifacts/<target-id>/scope.yaml
  • Optional phase-owned intake records under artifacts/<target-id>/intake/

Exit Expectations

  • Target workspace exists and is addressable through --target <id>.
  • pipeline-state.yaml records the selected binary path.
  • scope.yaml records the selected functions, addresses, symbols, or explicit whole-target scope.
  • Ghidra discovery and binary inspection have been run and reviewed.

Constraints

  • Do not run actual Ghidra analysis in this phase.
  • Do not write baseline, evidence, decompilation, or verification outputs.
  • Do not bypass ghidra-agent-cli workspace init, ghidra discover, or inspect binary for supported steps.
  • Do not create or run a new Ghidra script if the CLI lacks a capability; pause and ask the user first.

Next Step

  • P0 gate passes → headless-ghidra-baseline

What ships with it: 5 files

21.2 KB alongside SKILL.md

examples/

Keep looking

Skills are one crate of 326,984. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.