competition-agent-cloudlisted

# Competition Agent Cloud Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first. Use this skill when the challenge path is driven by prompt-to-tool execution, retrieval and memory boundaries, deployment drift, or build and release provenance. Reply in Simplified Chinese unless the user explicitly requests English. ## Quick Start 1. Decide whether the dominant path is agentic or infrastructure-driven. 2. Map one minimal control chain: untrusted input -> visible context -> tool or deployment side effect. 3. Distinguish checked-in intent from live runtime truth. 4. Keep prompts, tool args, manifests, mounts, and provenance steps in compact evidence blocks. 5. Reproduce the exploit or misconfiguration with minimal context and minimal instrumentation. ## Workflow ### 1. Agent And Prompt Injection - Treat prompts, tool schemas, retrieved chunks, planner notes, memory files, and handoffs as challenge artifacts. - Prove one minimal chain from untrusted content to model-visible instruction to tool side effect. - Distinguish claimed capability from runtime-exposed capability. ### 2. Cloud, Containers, And CI/CD - Split build-time, deploy-time, and runtime. - Reconcile compose or kube manifests with live mounts, env, logs, and traffic. - Trace provenance from source to depend