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 Nevaberry/nevaberry-plugins --skill devcontainers-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/nevaberry/nevaberry-plugins/devcontainers-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/devcontainers-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/devcontainers-knowledge-patch/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/nevaberry/nevaberry-plugins/devcontainers-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/devcontainers-knowledge-patch.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00009 | $0.01707 |
| Opus 5.5 | $0.00004 | $0.00683 |
| Sonnet 5.5 | $0.00002 | $0.00341 |
| Haiku 4.5 | $0.00001 | $0.00171 |
Grade A, and why
devcontainers-knowledge-patch 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dev Containers Knowledge Patch
Use this skill when configuring, building, running, or publishing Dev Containers, Features, and Templates. It is especially useful for lifecycle ordering, environment and user selection, metadata merging, lockfiles, dependency ordering, and current CLI behavior.
Reference index
| Reference | Topics |
|---|---|
| references/configuration-and-runtime.md | Configuration discovery, metadata merging, environments, workspaces, users, lifecycle, engines, paths, and runtime compatibility |
| references/lockfiles-and-cli.md | Feature lockfile format, frozen builds, maintenance commands, installation, and CLI limitations |
| references/feature-authoring.md | Feature packages, options, installers, users, lifecycle contributions, dependencies, ordering, idempotency, and publishing |
| references/template-authoring.md | Template layout, option substitution, optional paths, and OCI references |
Start with current behavior
Use the current lockfile name and flags
The generated Feature lockfile is .devcontainer-lock.json, beside
devcontainer.json. Current build and up commands generate it by default.
devcontainer build --frozen-lockfile
devcontainer up --no-lockfile
Use --frozen-lockfile in reproducible automation: it requires an existing
lockfile and rejects changes. Use --no-lockfile only when intentionally opting
out. The old --experimental-lockfile and
--experimental-frozen-lockfile spellings are deprecated and warn.
Features passed through --additional-features are deliberately excluded from
the lockfile. Do not rely on the lockfile to pin those additions.
Do not assume stop or down commands
The CLI does not implement devcontainer stop or devcontainer down. Teardown
automation must call the underlying container engine or orchestrator instead.
What ships with it
5 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 · 211 lines · 9 tokens per session scan A 389b626b71be
devcontainers-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (23 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 1,707 once invoked, about $0.0000 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 skills, from other repositories
k8s-sidecar-testing
Test the nat464-sidecar demo topology in a selected Kubernetes test namespace, verify IPv6 translation paths, and compare HTTP latency. Includes optional disposable Multipass/k3s setup.
helm
Helm chart authoring, templating, and release management for Kubernetes: charts, values, templating functions, repositories, dependencies, and lifecycle operations.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
polish-docs-meta
Finalize documentation and project metadata for a ship-ready MCP server. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.