Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add patelr3/agents/plugin install worktree-devcontainerWrote 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/patelr3/agents/dev-container)<a href="https://agentmods.dev/skills/patelr3/agents/dev-container"><img src="https://agentmods.dev/badge/skills/patelr3/agents/dev-container/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/patelr3/agents/dev-container"><img src="https://agentmods.dev/badge/skills/patelr3/agents/dev-container.svg" alt="Reviewed on agentmods" width="80" 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.00063 | $0.02340 |
| Opus 5.5 | $0.00025 | $0.00936 |
| Sonnet 5.5 | $0.00013 | $0.00468 |
| Haiku 4.5 | $0.00006 | $0.00234 |
Grade A, and why
dev-container 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Container Skill
Run work inside a dev container. This skill manages the full lifecycle: container build → AI tool execution → cleanup.
A sub-agent (Copilot, Claude, or AMP) runs inside the dev container to do the actual work. The parent session (you) manages the container lifecycle around it.
Inputs
When this skill is invoked, gather the following from the user or calling agent:
| Input | Required | Default | Description |
|---|---|---|---|
| Workspace folder | Yes | — | Path to the repo/worktree directory containing .devcontainer/ config |
| Prompt | No | — | Inline instructions for the sub-agent. Free-form text describing the work to do. |
| Plan file | No | — | Path to a file in the repo that describes the work (e.g., a PRD, a plan, a design doc). The sub-agent reads it and executes it. |
| Tool | No | copilot |
AI backend to run inside the container: copilot, claude, or amp. |
| Container name | No | Auto-derived from workspace | Name for the dev container instance. |
| Port offset | No | — | Integer for parallel port isolation (API = 3001 + N, Web = 3000 + N). |
| Auto-merge | No | true |
Whether to enable auto-merge on the created PR. |
| Create PR | No | true |
Whether to create a PR at the end. Set to false if the sub-agent handles PR creation itself. |
At least one of Prompt or Plan file must be provided. They can also be used together — the plan file provides the specification and the prompt provides additional context or instructions.
Execution Flow
Step 1: Resolve Inputs
Validate the workspace folder exists and contains a .devcontainer/ directory:
WORKSPACE_FOLDER="<workspace-folder>"
PROJECT_NAME="$(basename "$WORKSPACE_FOLDER")"
TOOL="<tool>" # copilot, claude, or amp — default: copilot
Auto-derive container name if not provided:
BRANCH_SUFFIX=$(cd "$WORKSPACE_FOLDER" && git rev-parse --abbrev-ref HEAD | sed 's|.*/||')
CONTAINER_NAME="${PROJECT_NAME}-${BRANCH_SUFFIX}"
What ships with it
6 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.
- 1mo ago First seen · 267 lines · 63 tokens per session scan A da662d5f5ac9
dev-container is a skill published in the GitHub repository patelr3/agents (2 stars, last pushed 6mo ago), licensed MIT. It adds 63 tokens to every session and 2,340 once invoked, about $0.0003 per session on Opus 5.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-08-31.
Other skills, from other repositories
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
bdd-container-update
Update the BDD test container image when its dependencies or runtime change. Determines version bump (major vs minor vs patch), rebuilds the Docker image, pushes to GitLab registry, and updates the image tag in starttest.sh. Test source (tests/, features/, scripts/, data/, conftest.py) is bind-mounted from the host…
docker-socket-mount
Docker / containerd socket mounted into a container → host RCE. Common in CI runners, GitOps controllers (ArgoCD, Flux), and 'Docker-in-Docker' setups. Single-command escape via docker run --rm --privileged -v /:/host alpine chroot /host.
securing-kubernetes-on-cloud
This skill covers hardening managed Kubernetes clusters on EKS, AKS, and GKE by implementing Pod Security Standards, network policies, workload identity, RBAC scoping, image admission controls, and runtime security monitoring. It addresses cloud-specific security features including IRSA for EKS, Workload Identity for…
detecting-privilege-escalation-in-kubernetes-pods
Detect and prevent privilege escalation in Kubernetes pods by monitoring security contexts, capabilities, and syscall patterns with Falco and OPA policies.
managing-astro-local-env
Manage local Airflow environment with Astro CLI (Docker and standalone modes). Use when the user wants to start, stop, or restart Airflow, view logs, query the Airflow API, troubleshoot, or fix environment issues. For project setup, see setting-up-astro-project.