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/the-biomechanist/windows-dev-agent/envgit clone --depth 1 https://github.com/The-Biomechanist/Windows-Dev-AgentWrote 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/the-biomechanist/windows-dev-agent/env)<a href="https://agentmods.dev/commands/the-biomechanist/windows-dev-agent/env"><img src="https://agentmods.dev/badge/commands/the-biomechanist/windows-dev-agent/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 | $0.00012 | $0.00083 |
| Opus 5 | $0.00006 | $0.00042 |
| Sonnet 5 | $0.00002 | $0.00017 |
| Haiku 4.5 | $0.00001 | $0.00008 |
Grade A, and why
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 4d 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
Use the bundled windows-dev-agent:env-inspect skill as the canonical procedure for this command.
If the user also asks about the surrounding agent/tool ecosystem, use ecosystem_scan only for the surfaces it actually establishes. Do not duplicate the skill's evidence, freshness, or package-routing rules in this Claude command adapter.
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.
- 4d ago First seen · 8 lines · 12 tokens per session scan A ffac4e3cbc8d
env is a command published in the GitHub repository The-Biomechanist/Windows-Dev-Agent (0 stars, last pushed 4d ago), licensed MIT. It adds 12 tokens to every session and 83 once invoked, about $0.0001 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 commands, from other repositories
fixlinks
Find replacement URLs for broken links using research agents.
rotatechangelog
Archive current changelog and start fresh.
setup
Full onboarding for a new project — runs /doctor diagnostics, then injects the CLAUDE.md template + nav-ref instrumentation + Zustand store exposure so the plugin works without the user having to read documentation.
run-action
Execute a learned Maestro flow ("action") by name with optional -e KEY=VALUE parameters. Looks the flow up via packages/rn-dev-agent-core/dist/learned-actions.js (same inventory as /rn-dev-agent:list-learned-actions), then replays it via cdprunaction — auto-repair-aware orchestration with structured RunRecords (GH.
end-session
Wrap up the work session with read-only evidence gathering, owner-classified documentation handoffs, gated issue sync, Kano refinement, and git hygiene checks.
test-feature
Test a React Native feature on the running simulator/emulator. Verifies UI, user flows, and internal state. Generates a persistent Maestro test file.