Borrowing it
Nothing to install: this file belongs to thecombatwombat/replicant-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/thecombatwombat/replicant-mcp/master/.claude/commands/check-env.mdgit clone --depth 1 https://github.com/thecombatwombat/replicant-mcpWrote 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/thecombatwombat/replicant-mcp/check-env)<a href="https://agentmods.dev/commands/thecombatwombat/replicant-mcp/check-env"><img src="https://agentmods.dev/badge/commands/thecombatwombat/replicant-mcp/check-env/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/commands/thecombatwombat/replicant-mcp/check-env"><img src="https://agentmods.dev/badge/commands/thecombatwombat/replicant-mcp/check-env.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.00014 | $0.00290 |
| Opus 5.5 | $0.00006 | $0.00116 |
| Sonnet 5.5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
check-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 1mo 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
Check Dev Environment
Run environment health checks and fix what you can. Report what needs manual action.
Step 1: Run checks
bash scripts/check-env.sh
Step 2: Act on results
For each warning:
- Tool version mismatch — If bd or gh is outdated locally, update
.tool-versionsand reinstall. If it's a remote-only issue, note it. - Plugin version mismatch — Tell the user to run
/plugin update beads@beads-marketplace. - bd doctor warnings — Run
bd doctor --fix(pipeecho Yfor confirmation). For unfixable items, report them. - Uncommitted changes — List the files. Ask if the user wants to commit or stash.
- Unpushed commits — Ask if the user wants to push.
- Stale worktrees — List them. Ask if the user wants to clean up.
- node_modules missing — Run
npm install.
Step 3: Verify
Run bash scripts/check-env.sh again to confirm all warnings are resolved. Report any remaining issues that need manual action.
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.
- 1mo ago First seen · 31 lines · 14 tokens per session scan A fdd632bcce9a
check-env is a command published in the GitHub repository thecombatwombat/replicant-mcp (18 stars, last pushed 3mo ago), licensed MIT. It adds 14 tokens to every session and 290 once invoked, about $0.0001 per session on Opus 5.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-30.
Other commands, from other repositories
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
auditar-cascading
Invoca cascading-failures-auditor — audita serviço para 5 triggers de cascade (sem timeout, retry sem jitter, sem circuit breaker, sem deadline, queue unbounded) e gera CASCADING-AUDIT.md.
react-native
Command "react-native" from getsentry/toolkit, covering xcode build step (react-native xcode) and important notes.
http-service
Build, review or debug a Bun HTTP service. Loads the http-service skill, then works the task through its workflow.
doctor
Diagnosticar y reparar problemas del framework Don Cheli, git y entorno. Usa cuando el usuario dice "doctor", "problemas del framework", "don cheli no funciona", "repair Don Cheli", "debug setup", "setup broken", "framework broken", "reparar entorno". Detecta y repara issues de configuración, git y dependencias…
doctor
Badi configuration validation. Checks all Badi components and produces a diagnostic report.