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 agentmods add commands/mitulgarg/env-doctor/wslgit clone --depth 1 https://github.com/mitulgarg/env-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/commands/mitulgarg/env-doctor/wsl)<a href="https://agentmods.dev/commands/mitulgarg/env-doctor/wsl"><img src="https://agentmods.dev/badge/commands/mitulgarg/env-doctor/wsl.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 | $0.00000 | $0.01196 |
| Opus 5 | $0.00000 | $0.00598 |
| Sonnet 5 | $0.00000 | $0.00239 |
| Haiku 4.5 | $0.00000 | $0.00120 |
Grade B, and why
wsl scanned grade B with 1 finding 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 5d 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.
Asks for rootmediumPrivilege escalation
A mod that escalates privileges can change anything on the machine, not only the project.
→ Remove the internal NVIDIA driver: sudo apt remove --purge nvidia-* libnvidia-* How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
wsl
Display comprehensive WSL environment information and GPU forwarding diagnostics.
Usage
env-doctor wsl [--json]
Options
| Option | Description |
|---|---|
--json |
Output results in JSON format for programmatic consumption |
Description
The wsl command runs a dedicated WSL environment analysis. It detects whether you are running inside WSL1, WSL2, or native Linux and — for WSL2 — validates the full GPU forwarding chain:
- Whether the internal NVIDIA driver (which breaks forwarding) is present
- Whether the WSL2 CUDA library (
/usr/lib/wsl/lib/libcuda.so) exists - Whether
nvidia-smiis reachable from inside WSL2 - Overall GPU forwarding status
!!! note This command only runs on Linux. On macOS or Windows it will exit with an error.
Example Output
WSL2 with GPU forwarding enabled
============================================================
🐧 DETAILED WSL ANALYSIS
============================================================
📌 Environment Type: WSL2
Kernel Version: 5.15.167.4-microsoft-standard-WSL2
🔍 GPU Forwarding Checklist:
✅ No internal NVIDIA driver (correct)
✅ WSL2 CUDA library found (/usr/lib/wsl/lib/libcuda.so)
✅ nvidia-smi working
✅ GPU Forwarding: Enabled
============================================================
WSL2 with GPU forwarding broken
============================================================
🐧 DETAILED WSL ANALYSIS
============================================================
📌 Environment Type: WSL2
Kernel Version: 5.15.167.4-microsoft-standard-WSL2
🔍 GPU Forwarding Checklist:
❌ Internal NVIDIA driver found (breaks GPU forwarding)
❌ WSL2 CUDA library missing (/usr/lib/wsl/lib/libcuda.so)
❌ nvidia-smi not working
❌ GPU Forwarding: Not working
⚠️ Issues Detected:
• NVIDIA driver installed inside WSL2 — this breaks GPU forwarding
💡 Recommendations:
→ Remove the internal NVIDIA driver: sudo apt remove --purge nvidia-* libnvidia-*
→ Install the NVIDIA driver on Windows, not inside WSL2
============================================================
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.
- 5d ago First seen · 186 lines · 0 tokens per session scan B bb5cfb4731d3
wsl is a command published in the GitHub repository mitulgarg/env-doctor (173 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,196 tokens. A static security scan graded it B with 1 finding (asks for root). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
add-language
新しい言語を piper-plus に追加するためのガイドです。引数 $ARGUMENTS に言語コード (例: de, it, da) を指定してください。.
review-language
Command "review-language" from ayutaz/piper-plus, covering 新言語実装レビュー, 前提条件, レビュー手順, step 1: 10エージェント並列レビュー and step 2: レビュー結果集約.
initref
Build a reference for the implementation details of this project. Use provided summarize tool to get summary of the files. Avoid reading the content of many files yourself, as we might hit usage limits. Do read the content of important files though. Use the returned summaries to create reference files in /ref…
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.