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/debuggit clone --depth 1 https://github.com/mitulgarg/env-doctorWhat 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.00749 |
| Opus 5 | $0.00000 | $0.00375 |
| Sonnet 5 | $0.00000 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
debug 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 2d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
debug
Get detailed information from all detectors for troubleshooting.
Usage
env-doctor debug
What It Shows
All Detector Results
- Raw output from every registered detector
- Detection status (success, warning, error, not_found)
- Version information
Detection Metadata
- Internal detection methods used
- File paths examined
- Detailed status information
Registry Information
- List of all available detectors
- Detector execution order
Error Details
- Full exception traces
- Diagnostic information for failures
Example Output
🔍 DEBUG MODE - Detailed Detector Information
============================================================
Registered Detectors: cuda_toolkit, nvidia_driver, python_library, wsl2, cudnn
--- WSL2 ---
Status: Status.SUCCESS
Component: wsl2
Version: wsl2
Metadata: {
'environment': 'WSL2',
'gpu_forwarding': 'enabled',
'wsl_lib_path': '/usr/lib/wsl/lib',
'libcuda_found': True
}
--- NVIDIA DRIVER ---
Status: Status.SUCCESS
Component: nvidia_driver
Version: 535.146.02
Path: /usr/lib/x86_64-linux-gnu/libnvidia-ml.so.1
Metadata: {
'max_cuda_version': '12.2',
'detection_method': 'nvml',
'gpu_name': 'NVIDIA GeForce RTX 3090',
'gpu_memory': 24576
}
--- CUDA TOOLKIT ---
Status: Status.SUCCESS
Component: cuda_toolkit
Version: 12.1.1
Path: /usr/local/cuda-12.1
Metadata: {
'nvcc_path': '/usr/local/cuda-12.1/bin/nvcc',
'cuda_home': '/usr/local/cuda-12.1',
'multiple_installations': ['/usr/local/cuda-12.1', '/usr/local/cuda-11.8']
}
--- CUDNN ---
Status: Status.SUCCESS
Component: cudnn
Version: 8.9.7
Path: /usr/local/cuda-12.1/lib64/libcudnn.so.8
Metadata: {
'cuda_version': '12.x',
'header_path': '/usr/local/cuda-12.1/include/cudnn.h'
}
--- PYTHON LIBRARIES ---
Status: Status.SUCCESS
Component: python_library
Libraries: {
'torch': {
'version': '2.1.0+cu121',
'cuda_version': '12.1',
'detection_method': 'import'
},
'tensorflow': {
'status': 'not_installed'
}
}
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.
- 2d ago First seen · 137 lines · 0 tokens per session scan A b8dcf43f45b0
debug is a command published in the GitHub repository mitulgarg/env-doctor (172 stars, last pushed 3d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 749 tokens. 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 commands, from other repositories
add-language
新しい言語を piper-plus に追加するためのガイドです。引数 $ARGUMENTS に言語コード (例: de, it, da) を指定してください。.
pina-agentic
../../.opencode/commands/pina-agentic.md.
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.