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/evilfreelancer/secs/container-securitynpx skills add EvilFreelancer/secs --skill container-securitygit clone --depth 1 https://github.com/EvilFreelancer/secsWhat 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 | $0.00118 | $0.02387 |
| Opus 5 | $0.00059 | $0.01193 |
| Sonnet 5 | $0.00024 | $0.00477 |
| Haiku 4.5 | $0.00012 | $0.00239 |
Grade A, and why
container-security scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
| Kubescape | K8s security platform | `curl -s https://raw.githubusercontent.com/kubescape/kubescape/master/install.sh \| /bin/bash` | How it starts
The opening of the file, as written. The whole thing — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Container Security
Thin router for container and Kubernetes security assessments. Load the reference, workflow, or payload file you need — do not read all of them.
When to Use
- Scanning Docker/OCI images for CVEs (single image or pipeline)
- Generating or attesting SBOMs (Syft / CycloneDX / SPDX)
- Diffing SBOMs across releases to flag newly-introduced CVEs
- Auditing a live Kubernetes cluster (CIS / NSA / MITRE)
- Mapping K8s RBAC and finding privilege-escalation paths
- Reviewing NetworkPolicy coverage
- Authoring Falco / Tetragon runtime rules
- Analyzing or testing container escape vectors (authorized only)
- Docker daemon / host hardening review
Trigger Phrases
"scan this image", "trivy / grype / syft", "audit k8s cluster", "kube-bench", "kubescape", "run CIS benchmark", "check RBAC", "networkpolicy coverage", "falco rule", "container escape", "SBOM diff", "new CVEs since last release".
When NOT to Use This Skill
| Request | Use instead |
|---|---|
| Static scan of K8s YAML / Helm / Kustomize before deploy | iac-security |
| Terraform / CloudFormation / Pulumi misconfig | iac-security |
| EKS / GKE / AKS control-plane or managed-service misconfig | exploiting-cloud-platforms |
| Cloud IAM misconfiguration (beyond K8s RBAC) | exploiting-cloud-platforms |
| Application-code vulns inside the container | auditing-code-for-vulnerabilities |
| Third-party library CVEs at source-code level | auditing-supply-chain |
| API endpoints exposed by containerized services | testing-apis |
Rule of thumb: pre-deployment YAML → iac-security; running cluster or built image → this skill.
Decision Tree
Target?
|
|-- Built/registry image ----------> workflows/image_scan.md
| \-- two images to compare? --> workflows/sbom_diff.md (FLAGSHIP)
|
|-- Dockerfile source -------------> examples/vulnerable_dockerfile.md
| + hadolint (references/image_scanning.md)
|
|-- Live K8s cluster --------------> workflows/cluster_audit.md
| |-- RBAC deep-dive ----------> workflows/rbac_analysis.md
| |-- Network policy gap ------> workflows/network_policy_review.md
| \-- CIS benchmark only ------> references/kubernetes_hardening.md
|
|-- Runtime monitoring ------------> references/runtime_security.md
| + examples/falco_custom_rule.yaml
|
\-- Escape testing (authorized) --> references/container_escape.md
+ payloads/container_escape_poc.md
What ships with it
15 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.
- examples/falco_custom_rule.yaml 3.5 KB
- examples/vulnerable_dockerfile.md 3.5 KB
- payloads/container_escape_poc.md 7.7 KB
- references/bounty_patterns_2024_2026.md 8.5 KB
- references/container_escape.md 5.3 KB
- references/image_scanning.md 3.8 KB
- references/kubernetes_hardening.md 5.2 KB
- references/runtime_security.md 4.3 KB
- schemas/finding.json 3.1 KB
- templates/assessment_report_template.md 2.0 KB
- workflows/cluster_audit.md 2.6 KB
- workflows/image_scan.md 2.0 KB
- workflows/network_policy_review.md 2.2 KB
- workflows/rbac_analysis.md 2.6 KB
- workflows/sbom_diff.md 4.2 KB
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 · 196 lines · 118 tokens per session scan A 0ec55ffe0dab
container-security is a skill published in the GitHub repository EvilFreelancer/secs (10 stars, last pushed 23d ago), licensed Apache-2.0. It adds 118 tokens to every session and 2,387 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
Blue Team Defense & Hardening
System hardening, detection engineering, security baseline monitoring, patch management, defense-in-depth architecture, and security posture improvement.
analyzing-email-headers-for-phishing-investigation
Parse and analyze email headers to trace the origin of phishing emails, verify sender authenticity, and identify spoofing through SPF, DKIM, and DMARC validation.
analyzing-golang-malware-with-ghidra
Reverse engineer Go-compiled malware using Ghidra with specialized scripts for function recovery, string extraction, and type reconstruction in stripped Go binaries.
analyzing-prefetch-files-for-execution-history
Parse Windows Prefetch files to determine program execution history including run counts, timestamps, and referenced files for forensic investigation.
analyzing-ios-app-security-with-objection
Performs runtime mobile security exploration of iOS applications using Objection, a Frida-powered toolkit that enables security testers to interact with app internals without jailbreaking. Use when assessing iOS app security posture, bypassing client-side protections, dumping keychain items, inspecting filesystem…
add-tool
Use when adding a new cybersecurity tool to this installer. Walks through editing the right module file, adding to toolsconfig.json, running validators, and syncing MCP server data if needed. Triggers on phrases like "add tool", "add ", "register a new tool", "include X in the installer".