Saltar al contenido
Nuevo

DeepSeek V4.1 Flash gratis por 7 días: 10M tokens al día tras una recarga de $10 o más. Hasta el 30/11.

Cómo funciona
zhaoxuya520/competition-agent-cloudLinux, cloud y contenedores

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 instalaciones+3 en 7 días44,8 mil EstrellasMITsincronizado hace 2 horas

Instalar

¿Aún no tienes la CLI de NotHoly? Instálala primero.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install zhaoxuya520/competition-agent-cloud

Escribe en ⁦~/.notholy/skills⁩ después de comprobar la firma y el SHA-256.

FirmaFirmado, ed25519
wSD4rSzQke…8zIDsHDA==La CLI comprueba el SHA-256 y la firma antes de escribir cualquier archivo.
Paquete2a514fdb…9fc710c0
2a514fdb349d…25299fc710c03 archivos · ⁦2.2 KB⁩
EscaneoBajosin hallazgos
El escaneo no encontró nada que señalar en esta versión.Ver el escaneo completo
Fuentegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-agent-cloud@cab634b

Esta entrada todavía no está escrita en tu idioma, así que aparece en English.

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

Archivos de esta versión

Permisos

PermisoDeclaradoHallado en el escaneo
Lee archivosNoNo
Escribe archivosNoNo
Ejecuta comandos de shellNoNo
Usa la redNoNo
Usa conectoresNoNo
Controla un navegadorNoNo

Hallazgos del escaneo

Revisado el 13 nov 2026

El escaneo no encontró nada que señalar en esta versión.

Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.

VersiónPublicadaCommitSHA-256FirmaCambio de permisos
v2026.9.22-cab634b13 nov 2026cab634b2a514fdbFirmada–

Pregunta todo lo que tu alcance permite.

Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.

  1. 1/3

    Crea la cuenta

    Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.

    IndividualEmpresa
  2. 2/3

    Añade créditos

    Con tarjeta. Pagas por token, sin suscripción.

    $5.00recarga mínima
  3. 3/3

    Pregunta

    En el chat, o instala el CLI y ejecuta notholy login en tu terminal.

    $ notholy login