Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
zhaoxuya520/competition-agent-cloudLinux, cloud and containers

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-cloud

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
wSD4rSzQke…8zIDsHDA==The CLI checks the SHA-256 and the signature before it writes a file.
Package2a514fdb…9fc710c0
2a514fdb349d…25299fc710c03 files · ⁦2.2 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-agent-cloud@cab634b

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

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesNoNo
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

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.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.9.22-cab634bNov 13, 2026cab634b2a514fdbSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login