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/router-matrix.md
View on GitHub# Competition Sandbox Router Matrix
Use this file after the sandbox model is active and one dominant evidence type or blocker is visible.
## Default Rule
Start in `ctf-sandbox-orchestrator`. Route to a child skill only when the decisive unknown is narrower than the generic sandbox workflow.
All child `competition-*` skills are downstream-only modules. They should not be entered implicitly before `ctf-sandbox-orchestrator` has already established sandbox assumptions.
## Stay In Competition Sandbox When
- The task is still ambiguous across domains.
- You are only building the first node map or the first minimal path.
- Several domains are involved but none dominates yet.
- The main blocker is deciding which evidence matters first.
## Route By Dominant Surface
### Web And Runtime
- General site, API, auth, session, upload, worker, or hidden route behavior -> `$competition-web-runtime`
- Browser storage, service workers, Cache Storage, IndexedDB -> `$competition-browser-persistence`
- WebSocket or SSE handshake, subscriptions, reconnect logic, realtime frames -> `$competition-websocket-runtime`
- Host headers, vhost routing, reverse proxies, route-to-service resolution -> `$competition-runtime-routing`
- SSR loaders, templates, hydration payloads, render-layer enforcement drift -> `$competition-template-render-path`
- Source maps, build manifests, emitted bundles, chunk loading, runtime recovery -> `$competition-bundle-sourcemap-recovery`
- GraphQL schema, persisted query, RPC manifest, generated client, contract drift -> `$competition-graphql-rpc-drift`
- OAuth or OIDC redirect, callback, PKCE, claim acceptance -> `$competition-oauth-oidc-chain`
- JWT header, `kid`, `alg`, issuer, audience, role or claim confusion -> `$competition-jwt-claim-confusion`
- Upload parsing, archive extraction, preview conversion, deserialization -> `$competition-file-parser-chain`
- Queue payloads, retries, cron drift, worker-only behavior -> `$competition-queue-worker-drift`
- SSRF reachability, internal fetch pivots, metadata token extraction, token acceptance -> `$competition-ssrf-metadata-pivot`
- Race windows, ordering bugs, idempotency failures, timing-dependent state drift -> `$competition-race-condition-state-drift`
- Proxy/backend parse differentials, path normalization drift, framing ambiguity, smuggling -> `$competition-request-normalization-smuggling`
### Reverse, Exploit, DFIR, Binary
- Binary triage, exploit primitives, crash behavior, native reversing -> `$competition-reverse-pwn`
- Malware config, staged payload, beacon parameters, IOC decoding -> `$competition-malware-config`
- Firmware partitions, boot chains, update packages, extracted filesystem -> `$competition-firmware-layout`
- Packet captures, protocol reconstruction, stream rebuilding -> `$competition-pcap-protocol`
- Custom protocol replay, state machine, checksums, accepted session reproduction -> `$competition-custom-protocol-replay`
- Timeline reconstruction across disk, logs, PCAP, registry, mailbox -> `$competition-forensic-timeline`
### Crypto, Stego, Mobile
- Encoding chain, crypto boundary, stego media, mobile trust boundary -> `$competition-crypto-mobile`
- Encrypted ZIP/PKZIP, legacy ZipCrypto, known plaintext, `bkcrack` -> `$competition-zip-archive`
- Image, audio, video, document, trailer, metadata stego -> `$competition-stego-media`
- Android APK, Frida, signer logic, SSL pinning, native bridge -> `$competition-android-hooking`
- iOS IPA, Objective-C or Swift runtime, Keychain, pinning, deeplink -> `$competition-ios-runtime`
### Agent, Cloud, Container, Supply Chain
- Prompt injection, retrieval poisoning, planner drift, tool misuse -> `$competition-prompt-injection`
- Agent, cloud, CI/CD, container, supply-chain as a broad cluster -> `$competition-agent-cloud`
- Image layers, sidecars, mounts, runtime-vs-manifest mismatch -> `$competition-container-runtime`
- Registry provenance, dependency drift, build or release tampering -> `$competition-supply-chain`
- K8s API, service account, RBAC, admission/controller behavior -> `$competition-k8s-control-plane`
- Metadata service, workload identity, link-local credential path -> `$competition-cloud-metadata-path`
- Container-to-host boundary crossing, kernel preconditions, namespace or cgroup escape proof -> `$competition-kernel-container-escape`
### Identity And Windows
- Identity chain, Windows host evidence, enterprise messaging, mixed AD task -> `$competition-identity-windows`
- Host-to-host pivot, WinRM, SMB, RDP, accepted replay edge -> `$competition-windows-pivot`
- LSASS memory, ticket caches, replayable session material -> `$competition-lsass-ticket-material`
- DPAPI masterkeys, vault blobs, browser secret stores, unwrap-to-access chain -> `$competition-dpapi-credential-chain`
- Kerberos delegation, S4U, RBCD, delegated ticket acceptance -> `$competition-kerberos-delegation`
- AD CS template, PKINIT, enrollment rights, cert-based privilege -> `$competition-ad-certificate-abuse`
- Coercion primitive, relay target, forced auth acceptance -> `$competition-relay-coercion-chain`
- Mailbox rules, forwarding, OAuth consent, delegate abuse -> `$competition-mailbox-abuse`
- Linux secret replay, socket trust edges, SSH or token pivots, host-to-host Linux movement -> `$competition-linux-credential-pivot`
## Re-Route Rules
- If the current child skill stops matching the dominant blocker, return to `ctf-sandbox-orchestrator` and pick a narrower path.
- If the path broadens from a narrow child skill into a mixed-domain chain, return to `ctf-sandbox-orchestrator` and rebuild the route from the earliest uncertain step.
- Keep only one primary child skill active unless a second one is clearly needed for the next decisive boundary.
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 |