competition-agent-cloud
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
v2026.9.22-cab634b3 installs+3 in 7 days44.8K StarsMITsynced 2 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install zhaoxuya520/competition-agent-cloudWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package2a514fdb…9fc710c0
2a514fdb349d…25299fc710c03 files · 2.2 KBScanLowno findings
Sourcegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-agent-cloud@cab634b
On this page
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
- Decide whether the dominant path is agentic or infrastructure-driven.
- Map one minimal control chain: untrusted input -> visible context -> tool or deployment side effect.
- Distinguish checked-in intent from live runtime truth.
- Keep prompts, tool args, manifests, mounts, and provenance steps in compact evidence blocks.
- 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.mdfor 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
Files in this version
agents/1379 B
- openai.yaml379 B
references/11.1 KB
- agent-cloud.md1.1 KB
- SKILL.md3.9 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | No | No |
| Uses the network | No | No |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
The scan found nothing to flag in this version.
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.9.22-cab634b | Nov 13, 2026 | cab634b | 2a514fdb | Signed | – |
More from zhaoxuya520
All from this publisherMore in Linux, cloud and containers
See the category- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
- cloud-gcpnoorqureshi/cloud-gcp4
- container-image-hardeningsecurityskills/container-image-hardening3
- performing-cloud-incident-containment-proceduresmukul975/performing-cloud-incident-containment-procedures3
- implementing-taxii-server-with-opentaxiimukul975/implementing-taxii-server-with-opentaxii3
- detecting-cryptomining-in-cloudmukul975/detecting-cryptomining-in-cloud3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login