Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
zhaoxuya520/competition-agent-cloudLinux, cloud e 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 instalações+3 em 7 dias44,8 mil EstrelasMITsincronizado há 2 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
wSD4rSzQke…8zIDsHDA==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacote2a514fdb…9fc710c0
2a514fdb349d…25299fc710c03 arquivos · ⁦2.2 KB⁩
VarreduraBaixonenhum achado
A varredura não encontrou nada para apontar nesta versão.Ver a varredura completa
Fontegithub.com/zhaoxuya520/reverse-skill/tree/main/CTF-Sandbox-Orchestrator/competition-agent-cloud@cab634b

Este item ainda não foi escrito no seu idioma, então aparece em 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

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosNãoNão
Roda comandos no shellNãoNão
Usa a redeNãoNão
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

A varredura não encontrou nada para apontar nesta versão.

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.9.22-cab634b13 de nov. de 2026cab634b2a514fdbAssinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login