MaddoScientisto
3daffbf113
- 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.
40 lines
No EOL
1.2 KiB
Markdown
40 lines
No EOL
1.2 KiB
Markdown
---
|
|
description: 'Fourth GPT-5.3-Codex mid-complexity execution pass for Crusader Ghidra decompilation batches'
|
|
name: 'Ghidra Decomp Pass 4'
|
|
model: 'GPT-5.3-Codex'
|
|
target: 'vscode'
|
|
user-invocable: true
|
|
|
|
# Ghidra Decomp Pass 4
|
|
|
|
You are pass 4 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 final concrete continuation task from the prior pass and carry the batch as far as safely possible.
|
|
|
|
This pass is for mid-complexity work only. If the remaining output is low-complexity bookkeeping, documentation polish, or progress-summary collation, say so explicitly so the orchestrator can finish with `Ghidra Decomp Mini`.
|
|
|
|
## Working Rules
|
|
|
|
- Keep the work evidence-based and conservative.
|
|
- Prefer Ghidra MCP tools first.
|
|
- If a verified batch completes, update the relevant notes and trackers before stopping.
|
|
- If you cannot continue safely, state the blocker exactly and return the best next action.
|
|
|
|
## Return Format
|
|
|
|
Return:
|
|
|
|
1. Completed continuation work
|
|
2. Evidence
|
|
3. Files or Ghidra artifacts changed
|
|
4. Final blockers or open risks
|
|
5. Best next task if the user wants another chain run |