Decepticon is an autonomous red-team agent that coordinates AI agents, security tools, sandboxes, and supporting services for authorized cybersecurity assessments. Security researchers and red teams can run it through its Docker stack, cloud service, command-line interface, or Python SDK, with the catalogue entries representing its available skills.
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 agentmods add skills/purpleailab/decepticon/containernpx skills add PurpleAILAB/Decepticon --skill containergit clone --depth 1 https://github.com/PurpleAILAB/DecepticonWrote 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/purpleailab/decepticon/container)<a href="https://agentmods.dev/skills/purpleailab/decepticon/container"><img src="https://agentmods.dev/badge/skills/purpleailab/decepticon/container.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.00055 | $0.00702 |
| Opus 5 | $0.00028 | $0.00351 |
| Sonnet 5 | $0.00011 | $0.00140 |
| Haiku 4.5 | $0.00006 | $0.00070 |
Grade A, and why
container-overview 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 2d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- container — 92% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Container / Kubernetes Attack Category
This is a routing skill for cloud-native engagements. Identify the surface, then load the matching sub-skill.
Sub-skills
| Sub-skill | Covers | When to load |
|---|---|---|
| k8s-pod-escape | Privileged container, hostPath escape, hostPID + SYS_PTRACE, runC CVE chains, cgroup release agent | RCE inside a pod, goal is node compromise |
| k8s-rbac-abuse | auth can-i --list, pods/exec on privileged pods, secrets get/list, escalate verb, bind verb, impersonate, nodes/proxy |
You have a ServiceAccount token; goal is cluster-admin |
| docker-socket-mount | /var/run/docker.sock or containerd socket mounted in → instant host root |
CI runners, ArgoCD/Flux, DinD, Jenkins agents |
| container-cve | Catalog of high-impact runtime CVEs — Leaky Vessels, runC 2019-5736, BuildKit chain, CRI-O 2022-0811 | Container runtime version fingerprinted |
Quick routing
Container target identified?
├── You have RCE in a pod / container → k8s-pod-escape
├── You have a Kubernetes SA token → k8s-rbac-abuse
├── Socket mounted (`docker.sock`, etc.) → docker-socket-mount
├── Runtime version is old / vulnerable → container-cve
└── Unknown / all of above → start with k8s-pod-escape's Phase 1
Tooling
| Tool | Use |
|---|---|
kubectl |
API-level enumeration and abuse |
kube-hunter |
Automated cluster vulnerability scan |
kdigger |
In-cluster recon (Quarkslab) |
peirates |
Kubernetes-specific privilege escalation |
botb |
Container break-out (Brad-Beam et al.) |
nsenter |
Cross-namespace process / mount entry |
crictl / ctr / nerdctl |
containerd / CRI direct access |
What ships with it
4 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.
- 2d ago First seen · 47 lines · 55 tokens per session scan A 1af48431ab0f
container-overview is a skill published in the GitHub repository PurpleAILAB/Decepticon (5,451 stars, last pushed 6d ago), licensed Apache-2.0. It adds 55 tokens to every session and 702 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
analyzing-docker-container-forensics
Use when investigate compromised Docker containers by analyzing images, layers, volumes, logs, and runtime artifacts to identify malicious activity and evidence. Use when working with analyzing docker container forensics.
analyzing-kubernetes-audit-logs
Use when parses Kubernetes API server audit logs (JSON lines) to detect exec-into-pod, secret access, RBAC modifications, privileged pod creation, and anonymous API access. Builds threat detection rules from audit event patterns. Use when investigating Kubernetes cluster compromise or building k8s-specific SIEM…
redteam-container-detail-pack
Domain routing and boundary guidance for authorized container and orchestration security testing, including Docker escape, Kubernetes privilege escalation, image vulnerabilities, and service mesh bypasses. Use when a task belongs to the container testing domain and needs scope, evidence, pivot, or exit criteria.
k8s-security-policies
Implement Kubernetes security policies including NetworkPolicy, PodSecurityPolicy, and RBAC for production-grade security. Use when securing Kubernetes clusters, implementing network isolation, or enforcing pod security standards.
helm-chart-scaffolding
Design, organize, and manage Helm charts for templating and packaging Kubernetes applications with reusable configurations. Use when creating Helm charts, packaging Kubernetes applications, or implementing templated deployments.
interactive-dashboard
Interactive web dashboards: stock trackers, sector heatmaps, portfolio monitors — served via preview URL.