Iron Proxy Gateway for NanoClaw
nanocoai/nanoclaw
Installs or refreshes Iron Proxy and its Iron Control web console for NanoClaw, with a local Docker setup, database, credentials and a human approval bridge.
Review and improve container image/runtime protection for an owned application with tested compatibility.
Install Container Hardening
$ npx skills add WrongStack/WrongStack --skill container-hardening -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install WrongStack/WrongStack container-hardening --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/core/skills/container-hardening .claude/skills/container-hardening && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "container-hardening" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-hardening into .claude/skills/container-hardening/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-hardening", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-hardeningType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add WrongStack/WrongStack --skill container-hardening -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install WrongStack/WrongStack container-hardening --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/core/skills/container-hardening .agents/skills/container-hardening && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "container-hardening" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-hardening into .agents/skills/container-hardening/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-hardening", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WrongStack/WrongStack --skill container-hardening -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install WrongStack/WrongStack container-hardening --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/core/skills/container-hardening .cursor/skills/container-hardening && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "container-hardening" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-hardening into .cursor/skills/container-hardening/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-hardening", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/WrongStack/WrongStack.git --path packages/core/skills/container-hardening--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add WrongStack/WrongStack --skill container-hardening -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install WrongStack/WrongStack container-hardening --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/core/skills/container-hardening .gemini/skills/container-hardening && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "container-hardening" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-hardening into .gemini/skills/container-hardening/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-hardening", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install WrongStack/WrongStack container-hardeningInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add WrongStack/WrongStack --skill container-hardening -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/core/skills/container-hardening .github/skills/container-hardening && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "container-hardening" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-hardening into .github/skills/container-hardening/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-hardening", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add WrongStack/WrongStack --skill container-hardening -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install WrongStack/WrongStack container-hardening --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/WrongStack/WrongStack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/core/skills/container-hardening .opencode/skills/container-hardening && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "container-hardening" agent skill from https://github.com/WrongStack/WrongStack/tree/main/packages/core/skills/container-hardening into .opencode/skills/container-hardening/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "container-hardening", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
container-hardening- GitHub stars
- 371
- Token cost
- ~837 tokens
- SKILL.md length
- 287 words
- Files
- 1
- Skills in repo
- 100
- Repo updated
- First seen
- Licence
- MIT
At a glance
Review and improve container image/runtime protection for an owned application with tested compatibility.
- Works in 6 steps: Map the application required… → Use non-root execution, narrow writable… → Avoid privileged mode, unnecessary host… → …
- Reducing privileges
- SKILL.md covers Selection card, Overview, Rules and Workflow, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Container Hardening is an agent skill from WrongStack/WrongStack. Review and improve container image/runtime protection for an owned application with tested compatibility. Use when reducing privileges, protecting secrets or setting container resource/exposure policies; do not label every hardening preference a confirmed vulnerability.
Its SKILL.md is about 840 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Containers. It works with Docker. The repository describes itself as: An AI coding agent that reads your code, edits files, runs commands, and reasons through bugs — across a terminal REPL, a full-screen TUI, and a browser UI, while you keep your… The licence is MIT.
When your agent uses it
- Reducing privileges
- Protecting secrets
- Setting container resource/exposure policies
- Do not label every hardening preference a confirmed vulnerability
Example prompts
- “/container-hardening”
Requirements
- Docker
Workflow steps
6 steps, taken from the first numbered list in SKILL.md.
- Map the application required capabilities, files, network access and persisted data before restricting it.
- Use non-root execution, narrow writable paths and read-only filesystems where compatible.
- Avoid privileged mode, unnecessary host mounts and daemon-socket access; document any real requirement.
- Keep build/runtime credentials out of layers and logs; use supported secret mechanisms.
- Bound memory/CPU/processes according to measured needs and verify graceful degradation.
- Review image provenance/digests and advisory applicability; a scanner count alone does not determine release risk.
What it can do on your machine
Read from SKILL.md and the folder at commit a744bdc. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
docs.docker.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Container Hardening loads about 837 tokens when it runs. Until then it costs about 73 tokens; SKILL.md has 287 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from WrongStack/WrongStack at commit a744bdc, republished under its MIT licence (© WrongStack). 287 words, ~837 tokens.
Download SKILL.mdSave it as
.claude/skills/container-hardening/SKILL.md (or your agent's skills folder).- name
- container-hardening
- description
- Review and improve container image/runtime protection for an owned application with tested compatibility. Use when reducing privileges, protecting secrets or setting container resource/exposure policies; do not label every hardening preference a confirmed vulnerability.
- trigger
- Review and improve container image/runtime protection for an owned application with tested compatibility. Use when reducing privileges, protecting secrets or…
- version
- 1.0.1
- required-capabilities
- filesystem.read
- optional-capabilities
- filesystem.write, execution.shell, verification.run, web.research
- metadata.routing-group
- operations
- metadata.domain
- containers
Container Hardening
Selection card
- Task: Reduce container privilege and secret exposure. / TR: Container ayrıcalığını ve secret maruziyetini azalt.
- Start: Identify the authorized target, current health and rollback boundary.
- Finish: apply the acceptance checks below; report observed results and unresolved constraints.
Overview
Review and improve container image/runtime protection for an owned application with tested compatibility.
Use current Docker/OCI/runtime documentation and the deployed platform version. Checked Docker target: 29.9.0; apply settings supported by the actual runtime.
Rules
- Map the application required capabilities, files, network access and persisted data before restricting it.
- Use non-root execution, narrow writable paths and read-only filesystems where compatible.
- Avoid privileged mode, unnecessary host mounts and daemon-socket access; document any real requirement.
- Keep build/runtime credentials out of layers and logs; use supported secret mechanisms.
- Bound memory/CPU/processes according to measured needs and verify graceful degradation.
- Review image provenance/digests and advisory applicability; a scanner count alone does not determine release risk.
Workflow
- Inspect image/config and the actual exposure/ownership boundary.
- Record current privileges and source-supported risks.
- Apply a coherent narrow restriction set and rebuild/run the application.
- Exercise startup, persistence, shutdown and necessary network/device operations.
- Report implemented protections, compatibility checks and remaining justified privileges.
Before returning
Privilege requirements explicit; secrets excluded; protected configuration tested; findings and optional improvements distinguished.
Sources
Versioned facts checked 2026-10-09; refresh authoritative sources before new installs/upgrades. Docker security, Build secrets.
Skills in scope
- security-scanner — review owned source, configuration and dependency metadata for supported security findings with precise evidence and remediation.
- docker-deploy — docker deploy contracts and verification.
- compose-operations — operate and evolve multi-service Docker Compose environments with explicit networks, volumes and environment boundaries.
- kubernetes-operations — operate and deploy owned Kubernetes workloads with explicit cluster, namespace and rollout identity.
© WrongStack, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in packages/core/skills/container-hardening of WrongStack/WrongStack.
Open the folder on GitHubat commit a744bdc
Compare with similar skills
Container Hardening next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Container Hardening this skillWrongStack/WrongStack | 371 | — | ~837 | Automated safety check: Pass | MIT | |
| Iron Proxy Gateway for NanoClawnanocoai/nanoclaw | 31k | — | ~4.6k | Automated safety check: Notes | MIT | |
| GreptimeDB Dev Docker ImageGreptimeTeam/greptimedb | 6.7k | — | ~4k | Automated safety check: Notes | Apache-2.0 | |
| Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit | 260 | 6 repos | ~1.1k | Automated safety check: Notes | Custom licence | |
| LangBot Deployment Guidelangbot-app/LangBot | 18k | — | ~1.2k | Automated safety check: Notes | Apache-2.0 | |
| Build Openshell Mxc WindowsNVIDIA/OpenShell | 16k | — | ~4.9k | Automated safety check: Pass | Apache-2.0 |
Similar skills
GreptimeDB Dev Docker Image
GreptimeTeam/greptimedb
Packages a locally built GreptimeDB debug binary into a development-only Docker image for local-cluster testing, with an optional push to a dev registry.
Senior DevOps Toolkit
maslennikov-ig/claude-code-orchestrator-kit
Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…
LangBot Deployment Guide
langbot-app/LangBot
Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.
- Official
Build Openshell Mxc Windows
NVIDIA/OpenShell
Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.
- Official
Megatron-LM Base Image Bump
NVIDIA/Megatron-LM
Moves Megatron-LM CI to a newer NVIDIA PyTorch base image, updating both the GitHub and GitLab pins together and handling the CI follow-up.
More from WrongStack/WrongStack
All 100 skills in this repoTech Stack
WrongStack/WrongStack
Validate and upgrade dependencies against live registries and official migration guides in any ecosystem.
Skill Creator
WrongStack/WrongStack
Create, improve and validate WrongStack SKILL.md bundles with precise discovery, progressive resources and current runtime contracts.
Bug Hunter
WrongStack/WrongStack
A skill your agent uses when scanning source code for bugs, anti-patterns, code smells, or quality issues in a codebase, or when running a proof-driven bug hunt that must find, prove, fix, and…
Design Craft
WrongStack/WrongStack
Design or substantially improve user-facing interfaces with a product-specific visual direction, content hierarchy, and rendered critique.
Design Critique
WrongStack/WrongStack
A skill your agent uses to audit an interface that already exists and say precisely why it looks generated, templated, or unfinished — a scored rubric across composition, typography, color, states…
Mailbox Bridge
WrongStack/WrongStack
A skill your agent uses when external coding agents (Claude Code, Aider, custom scripts) need to participate in the project's shared WrongStack mailbox, or when a user asks to "expose the mailbox"…
Related
Works with
Categories
Questions about Container Hardening
What does Container Hardening do?
Review and improve container image/runtime protection for an owned application with tested compatibility. Container Hardening is an agent skill from WrongStack/WrongStack. Review and improve container image/runtime protection for an owned application with tested compatibility.
When should I use Container Hardening?
Container Hardening fits situations like: reducing privileges; protecting secrets; setting container resource/exposure policies; do not label every hardening preference a confirmed vulnerability.
How do I install Container Hardening in Claude Code?
Run `npx skills add WrongStack/WrongStack --skill container-hardening -a claude-code`. Or copy the skill folder (packages/core/skills/container-hardening in WrongStack/WrongStack) into .claude/skills/container-hardening in your project. Claude Code loads it when a task matches its description.
How do I install Container Hardening in Codex?
Run `npx skills add WrongStack/WrongStack --skill container-hardening -a codex`. Or copy the skill folder (packages/core/skills/container-hardening in WrongStack/WrongStack) into .agents/skills/container-hardening in your project. Codex loads it when a task matches its description.
Can I use Container Hardening in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add WrongStack/WrongStack --skill container-hardening -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/container-hardening, .gemini/skills/container-hardening, .github/skills/container-hardening and .opencode/skills/container-hardening in your project.
What does Container Hardening need to run?
SKILL.md names no scripts, command-line tools or credentials: Container Hardening is instructions for the agent only. Our summary lists: Docker.
Does Container Hardening access the network?
SKILL.md names 1 domain. As links in the text: docs.docker.com. This is read from the text; nothing was executed.
Is Container Hardening safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Container Hardening use?
Container Hardening is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Container Hardening use?
About 837 tokens (SKILL.md is roughly 3.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Container Hardening?
Skills that share tags, products or a category with Container Hardening: Iron Proxy Gateway for NanoClaw (nanocoai/nanoclaw, 31k stars), GreptimeDB Dev Docker Image (GreptimeTeam/greptimedb, 6.7k stars), Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars) and LangBot Deployment Guide (langbot-app/LangBot, 18k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Container Hardening?
WrongStack (a GitHub organization) maintains it in WrongStack/WrongStack, which has 371 GitHub stars. The repository holds 100 skills in this directory. The repository was last updated on October 10, 2026.
Source: WrongStack/WrongStack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.