AGENT SKILL

competition-container-runtime

Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is consumed, how a sidecar or init container changes runtime state, or which route resolves to which live container. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

License 许可
MIT
最近更新
2026-10-15
Stars
★ 42
Forks
24

01 前言 Front Matter

name
competition-container-runtime
description
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for live container runtime analysis, mounted secrets, sidecars, namespaces, init containers, entrypoint drift, and route-to-container resolution. Use when the user asks why a live container differs from manifests, where a mounted secret is consumed, how a sidecar or init container changes runtime state, or which route resolves to which live container. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.

02 资源文件 2

03 SKILL.md 正文

Competition Container Runtime

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 is really about what the live container or pod is doing now, not what the checked-in manifest claims it should do.

Reply in Simplified Chinese unless the user explicitly requests English.

Quick Start

  1. Split intent from reality: manifest, image, startup, live mount, live route, live process.
  2. Map host -> proxy -> container or pod -> mounted volume -> consuming process.
  3. Keep secrets, rendered config, init output, and sidecar output separate from static manifests.
  4. Prove one minimal live path from mounted or injected state to reachable behavior.
  5. Reproduce the effect with the smallest runtime-specific chain.

Workflow

1. Map The Live Runtime

  • Compare compose or kube manifests against running containers, pods, mounted volumes, env, sidecars, init containers, and entrypoints.
  • Identify which process actually consumes the mounted secret, rendered config, or shared volume output.

2. Trace Route And Mount Boundaries

  • Map virtual host, reverse proxy, service, container port, filesystem mount, and runtime-generated file paths together.
  • Record whether the decisive state is image-baked, env-injected, mounted later, or written by an init/sidecar process.

3. Report The Runtime Deviation

  • State the earliest point where live runtime diverges from checked-in intent.
  • Keep one compact evidence chain from manifest or compose intent to live consumer behavior.

Read This Reference

  • Load references/container-runtime.md for the runtime checklist, mount-chain checklist, and common live-vs-static pitfalls.
  • If the hard part is kube API permissions, service-account trust, RBAC edges, admission mutations, or controller-created workload drift, prefer $competition-k8s-control-plane.
  • If the hard part is Host-header routing, path-prefix rewriting, or route-to-service mapping across nodes, prefer $competition-runtime-routing.
  • If the hard part is proving container-to-host crossover, kernel attack-surface preconditions, or stable escape primitives, prefer $competition-kernel-container-escape.
  • If the hard part is replaying Linux secrets, socket trust edges, or host-to-host pivots after container foothold, prefer $competition-linux-credential-pivot.

What To Preserve

  • Compose/Kubernetes fragments tied to live mounts or routes
  • Container IDs, pod names, mount paths, sidecar outputs, rendered config paths, and consuming processes
  • The exact route or file path that becomes reachable only at runtime

04 同仓库更多 Skills

longwangjiang88
longwangjiang88/SusuAIOverclock-pojia

yingan-tuoxiu

Owner-authorized YingAn/YingPo Android APK shell rehydration and stable rebuild workflow. Use for APKs with tiny or abnormal root DEX files, v.m.p or abcd655xx shell callbacks, libabcd/lib*shellservice_dex native loaders, protected assets, runtime-loaded DEX images, hidden real Application or Activity routes, and native lifecycle wrappers that must be recovered into a normally installable, signed multidex APK without changing product authentication or business authorization behavior.

★ 42
longwangjiang88
longwangjiang88/SusuAIOverclock-pojia

reverse-engineering

Use when performing reverse engineering on any target: websites, desktop binaries (PE/ELF), mobile apps (APK/IPA), or network protocols. Covers web scraping/API reverse, disassembly and decompilation, Frida/Xposed hooking, il2cpp/Unity reverse, protocol capture and replay, encryption/signature analysis, and memory debugging. Triggers: 逆向、反编译、Hook、脱壳、抓包、协议分析、Frida、Xposed、il2cpp、Unity逆向、 内存扫描、DLL注入、PE分析、ELF分析、APK逆向、IPA逆向、反混淆、签名分析、加密还原、 smali、Ghidra、IDA、Cheat Engine、mitmproxy、Wireshark、脱壳、加固、SO逆向、Web逆向。

★ 42
longwangjiang88
longwangjiang88/SusuAIOverclock-pojia

game-hacking

游戏辅助开发全链路助手——覆盖内存读写、协议分析、反编译、Hook 技术、驱动级隐藏、自动化脚本。 支持 C/C++、Python、x86/x64 汇编、DirectX/OpenGL。适用于 PC 端游、Android/iOS 手游、主机游戏。 当用户提到以下任何关键词时必须触发:游戏外挂、游戏辅助、内存修改、CE教程、游戏Hook、 协议分析、反编译、驱动隐藏、游戏脚本、按键精灵、游戏逆向、内存扫描、指针追踪、DLL注入、 游戏破解、脱壳、抓包分析、Frida、Xposed、il2cpp、Unity逆向、UE4逆向、DirectX Hook、 OpenGL Hook、游戏自动化、坐标识别、模板匹配、游戏安全测试。

★ 42
longwangjiang88
longwangjiang88/SusuAIOverclock-pojia

supply-chain-security

暂无简介

★ 42
longwangjiang88
longwangjiang88/SusuAIOverclock-pojia

reverse-engineering

Provides reverse engineering techniques. Use when the main job is to understand how a compiled, obfuscated, packed, or virtualized target works before exploiting or solving it, including binaries, APKs, WASM, firmware, custom VMs, bytecode, malware-like loaders, and anti-debug or anti-analysis logic. Do not use it when the vulnerability is already understood and the remaining task is exploitation; use pwn instead. Do not use it for pure web workflows, log or disk forensics, or standalone crypto problems unless reversing the implementation is the real blocker.

★ 42
longwangjiang88
longwangjiang88/SusuAIOverclock-pojia

radare2

Use this skill whenever the user wants to analyze binaries with radare2/r2 from the command line, including reverse engineering, disassembly, function analysis, strings/import inspection, patching, binary diffing, hex inspection, or r2 scripting. Also use it when the user mentions PE/ELF/Mach-O/DEX/WASM files together with CLI analysis, `rabin2`, `rasm2`, `radiff2`, `r2pipe`, or asks for radare2 command help on Windows/Linux/macOS.

★ 42