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/initgit 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.00496 |
| Opus 5 | $0.00000 | $0.00248 |
| Sonnet 5 | $0.00000 | $0.00099 |
| Haiku 4.5 | $0.00000 | $0.00050 |
Grade A, and why
init 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.
What it actually says
init
Generate CI/CD integration files for your project.
Usage
env-doctor init --github-actions
What It Does
Creates a .github/workflows/env-doctor.yml file in your project that runs env-doctor check --ci on every push and pull request to main/master.
The generated workflow:
- Checks out your code
- Sets up Python
- Installs env-doctor
- Runs
env-doctor check --ciwith proper exit codes
Options
| Flag | Description |
|---|---|
--github-actions |
Generate a GitHub Actions workflow file |
--force |
Overwrite the file if it already exists |
Example
$ env-doctor init --github-actions
Created .github/workflows/env-doctor.yml
Next steps:
1. Review and edit .github/workflows/env-doctor.yml to fit your project
2. Commit and push to activate the workflow
Common customizations:
- Change Python version to match your project
- Change runner to [self-hosted, gpu] for GPU validation
- Add 'env-doctor cuda-info --json' for detailed CUDA reports
Generated Workflow
name: Validate ML Environment
on:
push:
branches: [main, master]
pull_request:
branches: [main, master]
jobs:
validate-env:
runs-on: ubuntu-latest
steps:
- name: Checkout code
uses: actions/checkout@v4
- name: Set up Python
uses: actions/setup-python@v5
with:
python-version: '3.10'
- name: Install env-doctor
run: pip install env-doctor
- name: Validate environment
run: env-doctor check --ci
After generating, customize the file to fit your project — change the Python version, switch to a GPU runner, or add extra steps like env-doctor cuda-info --json.
See Also
- CI/CD Integration Guide - Full CI/CD setup including GitLab CI, JSON parsing, and automated CUDA installation
- check Command - Details on
--ciand--jsonflags
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 · 82 lines · 0 tokens per session scan A 7c8d2cad8272
init 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 496 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
ci-monitor
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-watcher subagent to poll CI status and make decisions based on the results.
Deploy
Deploy application to production or staging.
gh-healthcheck
Run health check on GitHub Actions workflow.
release
You are a release agent for the Rivet project. Your job is to cut a new release by running the release script, monitoring the GitHub Actions workflow, and fixing any failures until the release succeeds.
pr-check
Run all local CI checks before creating a PR.
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).