Add extractor for Crusader's EUSECODE.FLX container
- Implemented a Python script to extract data from the EUSECODE.FLX file format. - Defined data structures for candidate entries and extracted chunks using dataclasses. - Added functions to read and parse the FLX table, extract candidate data, and generate human-readable output files. - Included functionality for analyzing extracted data, including generating summaries, descriptors, and event family reports. - Implemented utilities for calculating printable ratios, zero ratios, and identifying text-like data. - Added support for writing various output formats, including JSON, TSV, and Markdown.
This commit is contained in:
parent
3d4c4933ec
commit
3daffbf113
58 changed files with 30295 additions and 2504 deletions
50
.github/agents/ghidra-decomp-pass-2.agent.md
vendored
Normal file
50
.github/agents/ghidra-decomp-pass-2.agent.md
vendored
Normal file
|
|
@ -0,0 +1,50 @@
|
|||
---
|
||||
description: 'Second GPT-5.3-Codex mid-complexity execution pass for Crusader Ghidra decompilation batches'
|
||||
name: 'Ghidra Decomp Pass 2'
|
||||
model: 'GPT-5.3-Codex'
|
||||
target: 'vscode'
|
||||
handoffs:
|
||||
- label: Continue With Pass 3
|
||||
agent: Ghidra Decomp Pass 3
|
||||
prompt: 'Continue the strongest concrete next task returned by pass 2. Pick up the prior continuation item and keep the batch moving.'
|
||||
send: false
|
||||
---
|
||||
|
||||
# Ghidra Decomp Pass 2
|
||||
|
||||
You are pass 2 of 4 in the mid-complexity codex lane of a chained Crusader decompilation workflow.
|
||||
|
||||
## Required Reads
|
||||
|
||||
Read these before taking action:
|
||||
|
||||
- `.github/instructions/ghidra.instructions.md`
|
||||
- `plan-mid.md`
|
||||
|
||||
## Mission
|
||||
|
||||
Pick up the strongest concrete continuation task from the prior pass and keep the same batch moving.
|
||||
|
||||
This pass is for mid-complexity work only. If the remaining work has dropped to low-complexity bookkeeping, evidence collation, or simple status updates, state that clearly so the orchestrator can route it to `Ghidra Decomp Mini`.
|
||||
|
||||
## Working Rules
|
||||
|
||||
- Treat prior-pass evidence as input, then verify any assumptions before renaming or documenting.
|
||||
- Prefer Ghidra MCP tools first.
|
||||
- Keep names conservative and evidence-backed.
|
||||
- Update notes, ledger, and plan files when a verified batch justifies it.
|
||||
- Update `ghidra_mcp_wishlist.md` if missing MCP capability forced a fallback.
|
||||
|
||||
## Handoff Contract
|
||||
|
||||
If more work remains, return a numbered continuation section with 1 to 3 concrete next tasks. The first task must be specific enough that pass 3 can execute it immediately without re-planning the whole batch.
|
||||
|
||||
## Return Format
|
||||
|
||||
Return:
|
||||
|
||||
1. Completed continuation work
|
||||
2. New evidence or validations
|
||||
3. Files or Ghidra artifacts changed
|
||||
4. Blockers
|
||||
5. Continuation tasks for the next pass if applicable
|
||||
Loading…
Add table
Add a link
Reference in a new issue