competition-agent-cloud

Analyzes prompt-to-tool chains, deployment drift, and CI provenance in CTF sandbox challenges.

7|4|Updated Jun 22, 2026
One-click install
npx skills add https://github.com/dbx0/skills --skill competition-agent-cloud-dbx0
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: competition-agent-cloud
Source: https://github.com/dbx0/skills/tree/main/skills/ai-llm/prompt-injection/competition-agent-cloud
Command: npx skills add https://github.com/dbx0/skills --skill competition-agent-cloud-dbx0

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? CTF challenges involving AI agents, cloud, containers, and CI/CD often hide the flag in the gap between checked-in intent and live runtime truth. This Skill provides a structured methodology for proving minimal exploit chains across prompt injection, deployment drift, and supply-chain provenance under sandbox assumptions. ## Core Features & Use Cases - Agentic Path Analysis: Maps instruction layers, retrieval layers, memory, tool gates, and side effects to prove one minimal chain from untrusted content to tool side effect. - Cloud and Container Reconciliation: Compares compose or Kubernetes manifests against live mounts, environment variables, logs, and traffic across build-time, deploy-time, and runtime. - Supply-Chain Provenance Tracing: Tracks the chain from source to dependency resolution, build, publish, and runtime consumer, focusing on version drift and registry pulls. - Use Case: During a CTF, you face an AI agent whose retrieved documents influence tool calls backed by a containerized service. Use this Skill to prove the prompt-to-tool chain, reconcile the manifest with live mounts, and package compact evidence blocks. ## Quick Start Ask the agent to analyze the challenge's prompt-to-tool flow and reconcile the deployment manifests with live runtime state after the sandbox orchestrator has established assumptions.

Frequently Asked Questions about competition-agent-cloud

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I analyze prompt injection in a CTF AI agent challenge?

Map instruction layers, retrieval layers, memory, tool gates, and side effects, then prove one minimal chain from untrusted content to model-visible instruction to tool side effect. Keep prompts, retrieved chunks, planner transitions, and final tool arguments in a compact evidence block.

How to detect deployment drift between Kubernetes manifests and runtime?

Split analysis into build-time, deploy-time, and runtime, then reconcile checked-in compose or kube manifests against live mounts, environment variables, sidecars, logs, and traffic. Treat checked-in manifests as intent, not deployment truth.

When should I use this skill instead of a dedicated prompt injection skill?

Use it when the challenge path mixes agentic and infrastructure concerns, such as prompt-to-tool flows combined with cloud or CI/CD elements. If the task is purely about prompt-boundary abuse or retrieved-content drift, a dedicated prompt injection skill is preferred.

Can this skill be used without the sandbox orchestrator?

No, it is a downstream specialization that requires the orchestrator to have already established sandbox assumptions, node ownership, and evidence priorities. Without that routing, return to the orchestrator first.

What evidence should be preserved during a cloud supply-chain CTF challenge?

Preserve prompt snippets, retrieved chunks, planner transitions, final tool arguments, compose or Kubernetes fragments tied to live mounts, artifact hashes, dependency drift, CI steps, and the resulting runtime consumer.