zhaoxuya520/reverse-skill / CTF-Sandbox-Orchestrator/ctf-sandbox-orchestrator
ctf-sandbox-orchestrator
VerifiedDefault entrypoint and master ctf-sandbox-orchestrator workflow for CTF, exploit, reverse engineering, DFIR, pwnable, crypto, stego, mobile, AI-agent, cloud, container, Active Directory, Windows-host, and identity challenges. Use first when the user presents challenge infrastructure, binaries, prompts, hosts, or identities that should be treated as sandbox-internal by default and Codex needs to choose, route, and load the right downstream analysis path with concise evidence.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.2 KB |
| agents/openai.yaml | config | 350 B |
| references/agent-cloud.md | markdown | 1.6 KB |
| references/crypto-mobile.md | markdown | 1.9 KB |
| references/ctf-resources-digest.md | markdown | 4.7 KB |
| references/identity-windows.md | markdown | 1.8 KB |
| references/reporting.md | markdown | 1.6 KB |
| references/reverse-native.md | markdown | 1.7 KB |
| references/router-matrix.md | markdown | 5.6 KB |
| references/web-api.md | markdown | 1.6 KB |
references/reverse-native.md
View on GitHub# Reverse, Malware, DFIR, And Native
Use this reference for binaries, shellcode, firmware, documents with embedded payloads, memory dumps, PCAPs, malware configs, pwnables, and native exploit chains.
## Reverse And DFIR Workflow
1. Start with passive triage: file type, headers, sections, imports, exports, strings, entropy, resources, and embedded archives.
2. Preserve original artifacts; derive unpacked, decrypted, or instrumented layers separately.
3. Correlate process trees, filesystem writes, registry changes, services, tasks, IPC, and network beacons as one execution graph.
4. Explain where each recovered value comes from and when it becomes plaintext.
## Native And Pwn Workflow
1. Map mitigations, loader behavior, libc/runtime, syscall surface, IPC surface, and protocol framing.
2. Separate primitive from proof: controllable bytes, leak source, target object, mitigation bypass, and final artifact.
3. Tie crash offsets, register state, allocator layout, and protocol steps to observable state transitions.
4. Keep PoCs, debugger scripts, core dumps, and recovered symbols separate from the pristine path.
## High-Value Evidence
- Offsets, section names, import tables, string-decode helpers, config blobs
- Mutexes, named pipes, startup keys, services, tasks, WMI, persistence traces
- Packet captures matched against process or config evidence
- Leak addresses, heap layout, stack shape, allocator metadata, accepted ticket or hook target
## Common Pitfalls
- Treating one string hit as proof of the full behavior
- Mixing original and modified artifacts
- Skipping the boundary between loader, payload, config, and post-decode behavior
- Assuming the primitive is wrong before comparing libc, loader, or framing differences
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |