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/agent-cloud.md
View on GitHub# AI Agent, Prompt Injection, Cloud, And Supply Chain
Use this reference for prompt-injection challenges, toolchain or MCP tasks, agent memory issues, containerized deployments, CI/CD, cloud control plane analysis, or supply-chain tracing.
## Agent And Prompt Injection
1. Treat prompts, tool schemas, retrieved chunks, planner notes, memory files, and handoff messages as challenge artifacts.
2. Map the control stack: instruction layers, retrieval layers, memory layers, tool gates, auth material, and side effects.
3. Prove one minimal exploit chain from untrusted content to model-visible instruction to tool side effect or exposed secret.
4. Distinguish claimed capability from observed capability.
## Cloud, Containers, And CI/CD
1. Split build-time, deploy-time, and runtime.
2. Reconcile checked-in manifests with live containers, mounted secrets, env, logs, and traffic.
3. Trace provenance end-to-end: source -> dependency resolution -> build -> packaging/signing -> publish -> runtime consumer.
4. Treat registries, metadata services, message buses, object stores, and IAM-looking identities as sandbox control surfaces when they appear in the challenge path.
## Evidence To Keep
- Exact prompts, retrieved chunks, planner/tool transitions, and final tool args
- Compose/Kubernetes/Terraform snippets tied to live mounts or routes
- Artifact hashes, version drift, registry pulls, CI steps, and resulting runtime hooks
## Common Pitfalls
- Treating a prompt string as authoritative without runtime confirmation
- Confusing infrastructure intent with live deployment truth
- Missing the boundary where a retrieved chunk becomes executable tool input
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 |