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 ao92265/claude-code-playbook --skill check-envgit clone --depth 1 https://github.com/ao92265/claude-code-playbookWrote 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/ao92265/claude-code-playbook/check-env)<a href="https://agentmods.dev/skills/ao92265/claude-code-playbook/check-env"><img src="https://agentmods.dev/badge/skills/ao92265/claude-code-playbook/check-env.svg" alt="Measured on agentmods" 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.00089 | $0.00498 |
| Opus 5 | $0.00044 | $0.00249 |
| Sonnet 5 | $0.00018 | $0.00100 |
| Haiku 4.5 | $0.00009 | $0.00050 |
Grade A, and why
check-env 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.
What it actually says
Check Environment
Pre-flight environment check before starting dev work. Run this at the start of a session to avoid wasting time on infrastructure issues.
Steps
-
Check for running Docker containers that might conflict:
docker psto list running containers- Flag any containers using common ports (3000, 3001, 5432, 1433, 8080)
-
Check for port conflicts on common dev ports:
lsof -i :3000,3001,5432,1433,8080 2>/dev/nullto find processes using these ports- Report what's using each occupied port
-
Verify environment files exist:
- Check for
.envor.env.localin the current project - Warn if missing but don't expose contents
- Check for
-
Check Docker daemon is running (if project uses Docker):
docker info > /dev/null 2>&1to verify Docker is available
-
Check Node.js and npm/yarn availability:
node --versionandnpm --version
-
Verify git status and credentials:
git statusto show current branch and any uncommitted changesgh auth statusto verify GitHub credentials work- Test push access:
git ls-remote origin HEADto confirm remote connectivity
-
Check available memory for builds:
- Report current Node.js version and default heap size
- Recommend
NODE_OPTIONS='--max-old-space-size=4096'if project has large builds
-
Report a clean summary of findings with any issues flagged clearly.
Important
- Do NOT start fixing issues automatically — report them and ask what to do
- Do NOT expose .env file contents
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 · 54 lines · 89 tokens per session scan A 53a5ad42194a
check-env is a skill published in the GitHub repository ao92265/claude-code-playbook (10 stars, last pushed 20d ago), licensed MIT. It adds 89 tokens to every session and 498 once invoked, about $0.0004 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-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…
compute-env-setup
Set up a reproducible Feynman compute environment for research jobs. Use when a task needs Python/R packages, GPU libraries, containers, Modal, SSH, caches, or managed model runtime setup.
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.
implementing-rbac-hardening-for-kubernetes
Harden Kubernetes Role-Based Access Control by implementing least-privilege policies, auditing role bindings, eliminating cluster-admin sprawl, and integrating external identity providers.
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.