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.
npx skills add event4u-app/agent-config --skill devcontainergit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/devcontainer)<a href="https://agentmods.dev/skills/event4u-app/agent-config/devcontainer"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/devcontainer/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/event4u-app/agent-config/devcontainer"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/devcontainer.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.00043 | $0.01001 |
| Opus 5 | $0.00022 | $0.00500 |
| Sonnet 5 | $0.00009 | $0.00200 |
| Haiku 4.5 | $0.00004 | $0.00100 |
Grade A, and why
devcontainer 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 7d 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 — 127 lines — stays where its author put it; the contents beside it link to each section on GitHub.
devcontainer
When to use
Use this skill when working with DevContainer configuration, GitHub Codespaces setup, or development environment standardization.
Do NOT use when:
- Local Docker setup without Codespaces (use
dockerskill) - Production deployment (use
aws-infrastructureskill)
Procedure: Modify DevContainer
- Gather context — read
.devcontainer/devcontainer.json, check.devcontainer/for env files and docs, checkagents/overrides/skills/devcontainer.mdfor project-specific overrides. - Identify change type — classify: image change, feature addition, secret addition, extension change, or env var change.
- Make the change — edit
devcontainer.json(or related files). Follow conventions below for secrets, features, and environment variables. - Build and verify — run
devcontainer buildto confirm the container builds. Check that extensions load and ports forward correctly. - Document — if adding a new secret or dependency, update the onboarding docs in
.devcontainer/.
Architecture
Custom image
DevContainers typically use a pre-built custom image hosted on a container registry (GHCR, ECR, Docker Hub). Read devcontainer.json for the image URL.
The image should include:
- Language runtime (PHP, Node.js, Python, etc.)
- Package managers (Composer, npm, etc.)
- Common development tools
Features (installed on top of the image)
Common features:
| Feature | Purpose |
|---|---|
git |
Git version control |
github-cli |
GitHub CLI (gh) for API access |
docker-in-docker |
Run Docker inside the DevContainer |
Secrets management
Secrets can be managed via:
- File mounts:
.devcontainer/.secrets/<NAME>→/run/secrets/<NAME> - GitHub Codespaces secrets: configured in the repository settings
- Environment variables: in
.devcontainer/devcontainer.env
Read devcontainer.json for the actual secret definitions and requirements.
Workspace
- Workspace folder: typically
/workspaceor/workspaces/{repo-name} - Mount type: bind mount from local workspace
- Container name and hostname: defined in
devcontainer.json
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.
- 7d ago First seen · 127 lines · 43 tokens per session scan A 24b3aa751769
devcontainer is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,001 once invoked, about $0.0002 per session on Opus 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-09-03.
Other skills, from other repositories
github-actions-templates
Create production-ready GitHub Actions workflows for automated testing, building, and deploying applications. Use when setting up CI/CD with GitHub Actions, automating development workflows, or creating reusable workflow templates.
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
devops-infrastructure
Guides Docker, CI/CD pipelines, deployment strategies, infrastructure as code, and observability setup. Use when writing Dockerfiles, configuring GitHub Actions, planning deployments, setting up monitoring, or when asked about containers, pipelines, Terraform, or production infrastructure.
harness
To build an AI harness: run, observe, validate, automate repeated work faster — CLI/MCP actions, devcontainers, skills, subagents, hooks, pipelines, automations.
qdrant-deployment-options
Guides Qdrant deployment selection. Use when someone asks 'how to deploy Qdrant', 'Docker vs Cloud', 'local mode', 'embedded Qdrant', 'Qdrant EDGE', 'which deployment option', 'self-hosted vs cloud', or 'need lowest latency deployment'. Also use when choosing between deployment types for a new project.
module-scaffold
Given a component name, generate a complete standalone ODH module operator repository. Produces Go module, CRD types implementing PlatformObject, controller skeleton with reconciler builder pattern, Helm chart, Makefile, CI config, singleton webhook, and AGENTS.md. Use when starting a new module from scratch.