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 killernay/cc-devenv-doctor --skill environment-doctorgit clone --depth 1 https://github.com/killernay/cc-devenv-doctorWrote 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/killernay/cc-devenv-doctor/environment-doctor)<a href="https://agentmods.dev/skills/killernay/cc-devenv-doctor/environment-doctor"><img src="https://agentmods.dev/badge/skills/killernay/cc-devenv-doctor/environment-doctor/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/killernay/cc-devenv-doctor/environment-doctor"><img src="https://agentmods.dev/badge/skills/killernay/cc-devenv-doctor/environment-doctor.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.00041 | $0.01193 |
| Opus 5 | $0.00020 | $0.00596 |
| Sonnet 5 | $0.00008 | $0.00239 |
| Haiku 4.5 | $0.00004 | $0.00119 |
Grade C, and why
environment-doctor scanned grade C with 2 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 11d 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.
Downloads and executes remote codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- Missing Claude Code CLI → `curl -fsSL https://claude.ai/install.sh | bash` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Missing Claude Code CLI → `curl -fsSL https://claude.ai/install.sh | bash` How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Every check below is read-only and pre-approved in allowed-tools, so run them
without stopping to ask. Never assume a result — always run the real command.
1. Run these checks (via the Bash tool, one at a time)
git --versionnode --version(needs ≥ 18, ≥ 20 recommended since claude-mem requires Node ≥ 20)bun --version(claude-mem's hooks and worker daemon run on Bun — without it claude-mem installs but silently does nothing)code --versiondocker --versionanddocker info(confirms the engine is actually running, not just installed)claude --versiontest -d ~/.claude-mem(indicates claude-mem is installed)claude plugin listto see which plugins are installed, andclaude plugin marketplace listto see which marketplaces are registeredcode --list-extensionsand check for the recommended set:anthropic.claude-code,ms-azuretools.vscode-docker
Summarize the results as a ✅/❌ table before suggesting any fixes.
2. Fix commands by OS (ask which OS if unknown)
Windows (PowerShell, via winget):
- Missing Git →
winget install --id Git.Git -e - Missing Node →
winget install --id OpenJS.NodeJS.LTS -e - Missing Bun →
irm https://bun.sh/install.ps1 | iex(installs to%USERPROFILE%\.bun\binand only updates the persisted PATH — a terminal that was already open still won't see it) - Missing VS Code →
winget install --id Microsoft.VisualStudioCode -e - Missing Docker →
winget install --id Docker.DockerDesktop -e, then note it needs a restart + first manual launch (andwsl --installfirst if WSL2 isn't set up yet) - Missing Claude Code CLI →
irm https://claude.ai/install.ps1 | iex
macOS (via Homebrew):
- Missing Git/Node/Bun →
brew install git/brew install node/brew install bun - Missing VS Code →
brew install --cask visual-studio-code - Missing Docker →
brew install --cask docker, then note it needs to be opened manually once - Missing Claude Code CLI →
curl -fsSL https://claude.ai/install.sh | bash
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.
- 11d ago First seen · 72 lines · 41 tokens per session scan C 8aff63fd1677
environment-doctor is a skill published in the GitHub repository killernay/cc-devenv-doctor (13 stars, last pushed 1mo ago), licensed MIT. It adds 41 tokens to every session and 1,193 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
root-cause
Find the mechanism behind a failure instead of patching its symptom - reproduce first, one variable per experiment with the prediction written before the run, exit by naming the mechanism and pinning it with a failing test. Use for a bug, an unexplained red test, or a failure that will not reproduce.
stress-test
Use when a design, plan, or decision needs adversarial scrutiny before proceeding. Interrogates every branch of the decision tree, providing recommended answers and forcing explicit agreement or pushback. Triggers on "grill me", "stress test this", "poke holes", "challenge this design", or when…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
x-bug2rag
A knowledge-capture tool that turns reusable bug explanations into a local RAG collection, meaning a searchable store of text that an agent can retrieve later. It records the trigger, incorrect implementation, correct implementation, and observable difference.
x-cr
A software-correctness investigation skill for finding why code behaves differently from what was expected. It uses evidence from code paths, specifications, tests, logs, and changes to assess possible causes.
x-fix
A bug-fixing skill with separate paths for directly reported bugs, correctness-review findings, and failed verification or quality-gate reports. It records completed fixes and their validation in project reports.