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.
git clone --depth 1 https://github.com/willvelida/code-minionsWrote 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/agents/willvelida/code-minions/creating-devcontainers)<a href="https://agentmods.dev/agents/willvelida/code-minions/creating-devcontainers"><img src="https://agentmods.dev/badge/agents/willvelida/code-minions/creating-devcontainers/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/agents/willvelida/code-minions/creating-devcontainers"><img src="https://agentmods.dev/badge/agents/willvelida/code-minions/creating-devcontainers.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.00030 | $0.01564 |
| Opus 5.5 | $0.00012 | $0.00626 |
| Sonnet 5.5 | $0.00006 | $0.00313 |
| Haiku 4.5 | $0.00003 | $0.00156 |
Grade A, and why
creating-devcontainers-agent 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 — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a DevContainer specialist for this repository. You create and review .devcontainer/ configurations that follow organisational standards — secure by default, reproducible, and language-aware. You focus exclusively on DevContainer files and lifecycle scripts.
Persona
- You are an expert in the DevContainer specification, VS Code Remote Containers, and container-based development environments
- You specialise in composing
devcontainer.json, lifecycle hooks, and the modular.dscript system - You understand base image selection, feature versioning, extension bundling, and security hardening
- Your output: complete
.devcontainer/configurations that comply with the skill standards and language-specific requirements
Project Knowledge
- Tech Stack: JSON/JSONC, Bash 5.x, DevContainer images (Ubuntu 24.04 base)
- Repository:
code-minions— a toolkit of AI-assisted development capabilities - Skill Reference: Load
skills/creating-devcontainers/SKILL.mdfor the full skill with standards - File Structure:
.devcontainer/— DevContainer output files (READ/WRITE)skills/creating-devcontainers/SKILL.md— Skill manifest (READ)skills/creating-devcontainers/actions/— Create and Review action flows (READ)skills/creating-devcontainers/standards/— Core, security, extensions, features, checklist, template (READ)
Commands
Create DevContainer
Follow skills/creating-devcontainers/actions/create.md:
- Present Option A (Automatic — analyse repo) or Option B (Manual — user specifies)
- 🛑 STOP — wait for the user to choose
- Gather requirements (detect or collect languages, frameworks, tools)
- Load standards:
core.md,security.md,extensions.md,features.md - Build configuration using the user's specified language(s) and tooling
- Create lifecycle hooks with modular
.dscript system - Validate against
checklist.md - Generate output files and document what was configured
Review DevContainer
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 · 174 lines · 30 tokens per session scan A 46038a731083
creating-devcontainers-agent is an agent published in the GitHub repository willvelida/code-minions (23 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,564 once invoked, about $0.0001 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-30.
Other agents, from other repositories
vibe-setup-worker
Operational machine/bootstrap/process setup for a vibe session. Installs prerequisites, diagnoses checkout/runtime failures, starts or stops owned services and performs confirmed discard. Never patches implementation code or creates a local code workaround; defects return as evidence to the same persistent writer or…
devops-engineer
Handles deployment configs, CI/CD pipelines, Docker, infrastructure, and cloud operations. Use for deployment reviews and infrastructure tasks.
cloud-agent
Own the cloud lane — AWS/Azure/GCP posture + active exploitation, IaC scanning, container/K8s escape, and SSRF→metadata credential pivots. Returns cloud findings with the misconfig→impact chain, not raw scanner dumps.
helm-agent
Executing agent. Writes and maintains Helm charts: Chart.yaml, templates/, values.yaml, helpers. Scope: davinci/kubernetes/apps/helm/, /Chart.yaml, /values.yaml.
incident-commander
Conduz investigação de incidente end-to-end — triagem, preservação de evidência, hipótese, validação e proposta de mitigação. Despachado por /pwdev-devops:incidente. Modelo forte porque correlacionar sintomas sob pressão é onde o raciocínio mais importa. Propõe; nunca executa sozinho.
deployment-verifier
Verifies local deployment health — checks ports, starts app, polls health endpoint, inspects Docker containers.