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 perniemann/pnCore --skill pn-dockergit clone --depth 1 https://github.com/perniemann/pnCoreWrote 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/perniemann/pncore/pn-docker)<a href="https://agentmods.dev/skills/perniemann/pncore/pn-docker"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-docker/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/perniemann/pncore/pn-docker"><img src="https://agentmods.dev/badge/skills/perniemann/pncore/pn-docker.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.00050 | $0.00645 |
| Opus 5.5 | $0.00020 | $0.00258 |
| Sonnet 5.5 | $0.00010 | $0.00129 |
| Haiku 4.5 | $0.00005 | $0.00064 |
Grade A, and why
pn-docker 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Docker
This SKILL.md is a router; load reference.md only when that workflow is active.
When to use
- Writing or reviewing a
Dockerfilefor a Node.js, Python, Go, or other service - Setting up
compose.yamlfor local development (databases, Redis, message queues) - Optimising image size, build speed, or layer caching
- Hardening a container: non-root user, read-only filesystem, security scanning
- Integrating Docker builds into CI/CD pipelines
For full Dockerfile examples, compose.yaml, and CI config, see reference.md.
Key rules
Multi-stage builds: Use at least two stages (deps/build → runner). Final stage uses alpine or distroless and a non-root user.
Layer caching: Copy dependency manifests first, install, then copy source code. Never COPY . . && RUN npm ci — invalidates cache on every source change.
.dockerignore: Always include — omitting it copies node_modules into the build context, slowing every build. Minimum: node_modules, .next, .git, local env/secret patterns (see reference.md), dist, coverage.
compose.yaml: Use target: build for local dev with volume mounts for live reload. Use service_healthy depends_on for databases.
Security hardening
| Practice | Why |
|---|---|
Non-root user (USER appuser) |
Limits blast radius of container escape |
| Read-only root filesystem | docker run --read-only --tmpfs /tmp |
No privileged: true |
Never in production |
| Pin base image versions | node:22.11.0-alpine not node:alpine |
| Scan with Trivy | trivy image myapp:latest in CI |
No secrets in ENV or ARG |
Use runtime secrets: Vault, AWS Secrets Manager |
| Minimal base image | alpine or distroless to reduce attack surface |
Image size targets
| Stack | Target compressed size |
|---|---|
| Node.js API (alpine) | < 150 MB |
| Next.js (standalone, alpine) | < 200 MB |
| Python FastAPI (slim) | < 120 MB |
| Go (scratch/distroless) | < 30 MB |
Guardrails
- Reference
pn-devops-automationfor full CI/CD pipeline patterns. - Reference
pn-observabilityforHEALTHCHECKendpoint implementation. - Reference
pn-monorepofor multi-service monorepo Docker build strategies. - Never use
latesttag in production manifests; always pin to a SHA or semver.
What ships with it
1 file 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 Changed · +2 lines b7bb66ffcd14
- 1mo ago First seen · 55 lines · 50 tokens per session scan A 80cd19724995
pn-docker is a skill published in the GitHub repository perniemann/pnCore (0 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 645 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
typescript
TypeScript coding conventions, best practices, and patterns for writing clean, maintainable code.
devops-deployment
Use when setting up CI/CD pipelines, containerizing applications, deploying to Kubernetes, or writing infrastructure as code. DevOps & Deployment covers GitHub Actions, Docker, Helm, and Terraform patterns.
typescript-development
You MUST activate this skill when working on TypeScript or JavaScript projects.
js-gof
Apply Gang of Four and related design patterns in JavaScript and TypeScript. Use when implementing creational, structural, or behavioral patterns, or when the user mentions factories, builder, prototype, flyweight, singleton, object pool, adapter, wrapper, decorator, proxy, bridge, composite, facade, chain of…
error-handling
Apply error handling and recovery patterns in JavaScript/TypeScript or Node.js. Use when implementing error handling, retry logic, or when the user mentions domain errors, error recovery, error escalation.
codex-docs-drift-scout
Install the AutoHub docs-drift Codex automation from signed AutoVault skill resources and audit its render fidelity with autovault doctor.