Guide for setting up secured VS Code dev containers for coding agents. Use when creating or hardening a DevContainer to sandbox Claude Code or other coding agents, configuring Docker socket proxies, handling VS Code IPC escape vectors, setting up git worktree support, or verifying security controls. Covers threat model, three-layer defence architecture, Node.js/pnpm setup, and verification testing.
95
95%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Advisory
Suggest reviewing before use
Security
2 findings — 2 medium severity. This skill can be installed but you should review these findings before use.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
Third-party content exposure detected (high risk: 1.00). The skill's startup commands (see NODE-SETUP.md and the Docker Compose command in SECURITY-HARDENING.md) explicitly curl and pipe the external URL https://claude.ai/install.sh into bash at container startup, which fetches and executes untrusted third-party code that can materially influence agent behavior.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
Potentially malicious external URL detected (high risk: 1.00). The devcontainer startup command performs a runtime fetch-and-execute of remote code via "curl -fsSL https://claude.ai/install.sh | bash", which runs external code during container start and is relied on to install the claude CLI, so it directly executes remote code at runtime.