competition-agent-cloud — Claude Code skill: install
The competition-agent-cloud Claude Code skill investigates agent and cloud paths in CTF sandboxes. It is routed in after the orchestrator sets the sandbox assumptions, for tracing input-to-tool actions or deployment behavior.
MIT 109 installs ★ 45,047 updated 2026-09-22
npx skills add zhaoxuya520/reverse-skill --skill competition-agent-cloud -a claude-codeWhat competition-agent-cloud does
The skill examines CTF challenges involving AI agents, cloud infrastructure, and build or release chains. It traces how untrusted content reaches a model-visible instruction and triggers a tool action. It also compares deployment configuration with live system state and artifact provenance.
It starts by choosing an agent-led or infrastructure-led path, then maps a minimal evidence chain. $ctf-sandbox-orchestrator must first establish sandbox assumptions, node ownership, and evidence priorities. For narrower topics, the workflow points to dedicated skills. Replies default to Simplified Chinese unless English is requested.
What it helps with
- trace untrusted content from model context to a tool action
- compare deployment manifests with live mounts and environment
- follow a dependency from source through build to runtime use
- connect CI steps to published artifacts consumed by a service
Example prompts for the agent
- Trace how untrusted retrieved text leads to a tool call in this sandbox challenge.
- Compare the Kubernetes manifests with the running application's mounts and environment.
- Follow this dependency from source through publication to the running service.
How to install competition-agent-cloud
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-agent-cloud -a claude-code2Manually: put the files in place
~/.claude/skills/competition-agent-cloud/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/competition-agent-cloud/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-agent-cloud -a codex2Manually: put the files in place
.agents/skills/competition-agent-cloud/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-agent-cloud -a cursor2Manually: put the files in place
.cursor/skills/competition-agent-cloud/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install zhaoxuya520/reverse-skill CTF-Sandbox-Orchestrator/competition-agent-cloud/SKILL.md2Manually: put the files in place
.github/skills/competition-agent-cloud/SKILL.md1Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-agent-cloud -a gemini-cli2Platform CLI
gemini skills install https://github.com/zhaoxuya520/reverse-skill --path CTF-Sandbox-Orchestrator/competition-agent-cloudManually: put the files in place
.devin/skills/competition-agent-cloud/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add zhaoxuya520/reverse-skill --skill competition-agent-cloud -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about competition-agent-cloud
How do I install competition-agent-cloud in Claude Code?
Run npx skills add zhaoxuya520/reverse-skill --skill competition-agent-cloud -a claude-code. The skill file is at ~/.claude/skills/competition-agent-cloud/SKILL.md.
What does competition-agent-cloud do?
It investigates agent and cloud CTF scenarios, tracing untrusted input to tool actions and comparing deployment configuration with live infrastructure.
What does competition-agent-cloud require?
$ctf-sandbox-orchestrator must establish the sandbox assumptions, node ownership, and evidence priorities before routing a task here.
Source text
SKILL.md · MIT
--- name: competition-agent-cloud description: Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for AI-agent, prompt-injection, MCP or toolchain, cloud, container, CI/CD, and supply-chain challenges. Use when the user asks to analyze prompt-to-tool flows, retrieval poisoning, mounted secrets, deployment drift, runtime-vs-manifest mismatches, registry provenance, or CI-produced artifacts under sandbox assumptions. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here. --- # 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 dependency resolution to build to publish to runtime consumer. ## Read This Reference - Load `references/agent-cloud.md` for the control-stack checklist, deployment-truth checklist, and evidence packaging. - If the task is specifically about prompt-boundary abuse or retrieved-content-to-tool drift, prefer `$competition-prompt-injection`. - If the task is specifically about CI, dependency provenance, registry drift, or shipped artifacts, prefer `$competition-supply-chain`. - If the task is specifically about queue payloads, async worker drift, retries, or worker-only runtime state, prefer `$competition-queue-worker-drift`. - If the task is specifically about SSRF to internal control surfaces, metadata endpoints, or metadata-derived token pivots, prefer `$competition-ssrf-metadata-pivot`. - If the task is specifically about proxy-upstream parse differentials, ambiguous headers, path normalization drift, or request smuggling behavior, prefer `$competition-request-normalization-smuggling`. - If the task is specifically about metadata-service access, instance or workload identity, link-local token paths, or metadata-derived privilege, prefer `$competition-cloud-metadata-path`. - If the task is specifically about kube API permissions, service-account trust, admission behavior, controller drift, or cluster secret exposure, prefer `$competition-k8s-control-plane`. - If the task is specifically about live mounts, sidecars, init containers, or runtime-only secret exposure, prefer `$competition-container-runtime`. - If the task is specifically about container-to-host boundary crossing, kernel-surface prerequisites, or escape primitive verification, prefer `$competition-kernel-container-escape`. ## What To Preserve - Prompt snippets, retrieved chunks, planner transitions, and final tool args - Compose or Kubernetes fragments tied to live mounts or routes - Artifact hashes, dependency drift, CI steps, and the resulting runtime consumer
© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill