Orchestrator Container Spawn
Spawning and hardening scan containers from the recon orchestrator: the security flags...
Install
npx skills add samugit83/redamon --skill orchestrator-container-spawn -g -a claude-code -y- Repository
- samugit83/redamon3.3k
- Category
- Security
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 1,825 tokens
- Runs scripts
- No, instructions only
What it does
Spawning and hardening scan containers from the recon orchestrator: the security flags that look correct and break the container, and the sibling bind-mount path handling. cap_drop and no-new-privileges were each reverted after breaking real scans. Trigger: editing recon_orchestrator/container_manager.py; changing how a scan container is spawned or hardened; touching _scanner_hardening, sibling_host_path, cap_drop, security_opt, or a bind mount for a spawned container.
When to Use
- Changing how the orchestrator launches or secures a scan container (recon_orchestrator/container_manager.py).
For the no-env_file knob rule, see the recon_orchestrator
AGENTS.md CRITICAL RULES (not repeated here).
