headless-ghidra-evidence
P2 phase skill for Headless Ghidra third-party evidence. Use after P1 to review baseline/runtime artifacts, identify or rule out third-party code, record pristine sources, classify functions, and capture evidence before metadata recovery.
How do I install this agent skill?
npx skills add https://github.com/bytelandtechnology/headless-ghidra --skill headless-ghidra-evidenceIs this agent skill safe to install?
- Gen Agent Trust Hubpass
This skill facilitates the identification and classification of third-party libraries within a Headless Ghidra analysis pipeline. It operates by reviewing artifact data generated from binary analysis. The primary security consideration is the ingestion of data derived from potentially untrusted external targets, creating an indirect prompt injection surface.
- Socketpass
No alerts
- Snykpass
Risk: LOW · No issues
What does this agent skill do?
Headless Ghidra Third-Party — P2
P2 reviews baseline and runtime YAML to identify third-party libraries, record
local pristine source directories, and classify functions for later metadata
enrichment. Source download or acquisition is outside the CLI; the CLI records
source_path, pristine_path, version, confidence, and evidence.
Required ghidra-agent-cli Commands
ghidra-agent-cli functions listghidra-agent-cli functions showghidra-agent-cli imports listghidra-agent-cli constants listghidra-agent-cli strings listghidra-agent-cli vtables listghidra-agent-cli types listghidra-agent-cli callgraph listghidra-agent-cli callgraph callersghidra-agent-cli callgraph calleesghidra-agent-cli third-party addghidra-agent-cli third-party noneghidra-agent-cli third-party set-versionghidra-agent-cli third-party listghidra-agent-cli third-party classify-functionghidra-agent-cli third-party vendor-pristineghidra-agent-cli execution-log appendghidra-agent-cli gate check --phase P2
Inputs
artifacts/<target-id>/baseline/functions.yamlartifacts/<target-id>/baseline/callgraph.yamlartifacts/<target-id>/baseline/types.yamlartifacts/<target-id>/baseline/constants.yamlartifacts/<target-id>/baseline/vtables.yamlartifacts/<target-id>/baseline/strings.yamlartifacts/<target-id>/baseline/imports.yamlartifacts/<target-id>/runtime/run-manifest.yamlartifacts/<target-id>/runtime/hotpaths/call-chain.yaml- Existing
artifacts/<target-id>/third-party/identified.yamlif present
Outputs
artifacts/<target-id>/third-party/identified.yamlartifacts/<target-id>/third-party/pristine/<library>@<version>/- Optional local adaptation changes under
artifacts/<target-id>/third-party/compat/<library>@<version>/
Exit Expectations
identified.yamlrecords at least one medium-or-higher confidence library when third-party code is present.identified.yamlrecordslibraries: []when review finds no third-party code.- Each recorded third-party library has a local
source_pathand a pristine directory underthird-party/pristine/. - Pristine source directories are kept unmodified; local adaptation edits live
under
third-party/compat/. - The next phase has enough version and function-classification evidence to recover names, signatures, and types.
Constraints
- Do not mutate baseline YAML exports directly.
- Do not claim unsupported evidence without recording the supporting source.
- Do not bypass
ghidra-agent-clifor supported baseline reads, third-party writes, or execution logging. - Do not create or run a new Ghidra script if the CLI lacks a capability; pause and ask the user first.
Next Step
- P2 gate passes →
headless-ghidra-discovery
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/bytelandtechnology/headless-ghidra/headless-ghidra-evidence">View headless-ghidra-evidence on skillZs</a>