Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Saprophytic-seattle561/reverse-skill --skill competition-kernel-container-escapegit clone --depth 1 https://github.com/Saprophytic-seattle561/reverse-skillWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/saprophytic-seattle561/reverse-skill/competition-kernel-container-escape)<a href="https://agentmods.dev/skills/saprophytic-seattle561/reverse-skill/competition-kernel-container-escape"><img src="https://agentmods.dev/badge/skills/saprophytic-seattle561/reverse-skill/competition-kernel-container-escape.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00102 | $0.00580 |
| Opus 5 | $0.00051 | $0.00290 |
| Sonnet 5 | $0.00020 | $0.00116 |
| Haiku 4.5 | $0.00010 | $0.00058 |
Grade A, and why
competition-kernel-container-escape scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
This is a copy
100% identical to competition-kernel-container-escape — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Competition Kernel Container Escape
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 decisive step is proving a boundary crossing between containerized context and host or higher-privilege kernel context.
Reply in Simplified Chinese unless the user explicitly requests English.
Quick Start
- Map runtime isolation first: namespaces, cgroups, seccomp, capabilities, LSM, and mount boundaries.
- Separate exploit prerequisite, primitive, and boundary-crossing proof.
- Record kernel version, config hints, runtime options, and reachable syscall surface.
- Keep instrumented observations separate from pristine challenge path.
- Reproduce one minimal primitive-to-boundary-crossing chain.
Workflow
1. Map Isolation And Kernel Surface
- Record namespace map, cgroup mode, capabilities, seccomp profile, AppArmor or SELinux state, mounted filesystems, and runtime sockets.
- Note kernel version, distro build hints, module exposure, and container runtime behavior.
- Keep host and container observations linked to exact node and context.
2. Prove Exploit Primitive And Crossover
- Show controllable input, trigger condition, affected object, and observable kernel or runtime state change.
- Capture before and after identity, namespace, mount, or process visibility to prove boundary crossing.
- Distinguish crash-only behavior from stable capability gain.
3. Reduce To Decisive Escape Chain
- Compress to: prerequisite state -> primitive trigger -> boundary crossing evidence -> resulting host-level capability.
- State whether root cause is kernel vulnerability, runtime misconfiguration, capability overgrant, or namespace leak.
- If path relies mostly on credential replay after initial foothold, hand off to Linux credential pivot skill.
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 51 lines · 102 tokens per session scan A c6e840b0365e
competition-kernel-container-escape is a skill published in the GitHub repository Saprophytic-seattle561/reverse-skill (1 stars, last pushed yesterday), licensed MIT. It adds 102 tokens to every session and 580 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to competition-kernel-container-escape, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
burp-scan
Burp Suite scanning via MCP tools — passive traffic analysis, active payload testing, OOB verification, and vulnerability reporting using Burp's proxy, HTTP sender, Collaborator, and scanner APIs. Use when the user has Burp Suite running with the AI Agent MCP server and wants to scan, test, or analyze web traffic…
ci-cd-expert
Enterprise CI/CD, optimization, security, & delivery expert. Covers GHA, GitLab CI, Jenkins, monorepos (Turbo, Nx, Bazel), containers (BuildKit, Kaniko), GitOps (Argo), delivery (Spinnaker, Kayenta, Fastlane, Flyway), OIDC, and Android. Use for: pipelines, caching, GitOps, monorepos, OIDC, DB migrations, mobile…
apple-container-expert
Expert guide for Apple's native container CLI (apple/container) — the open-source, Swift-native, VM-per-container runtime for Apple Silicon macOS. Read this skill BEFORE answering any question about: installing or starting apple/container; container run/build/machine/volume/network commands; configuring config.toml…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
argent-tv-interact
Control and inspect TV apps via argent — Apple TV (tvOS), Android TV (leanback), and Amazon Fire TV (Vega). Boot the target, read focus, navigate with the D-pad remote, type, screenshot, and on Vega debug the JS runtime (evaluate, console logs, network inspector). Use when a task targets a TV (runtimeKind "tv", or…
polar-local-environment
This skill should be used when setting up or managing Polar local development environment with Docker.