A command that checks whether a local development environment has the runtimes, databases, tools, and credentials a project needs. It reads the project's architecture requirements to decide what to check.

Checking readiness for local development on macOS, Ubuntu, or Windows. It helps verify project components such as frontend and backend runtimes, databases, frameworks, build tools, and integrations.

It helps find missing setup before development fails because a required tool, service, or credential is unavailable. The report includes platform-specific installation commands.

check-env — Command for Claude Code by navraj007in

Install

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.

Clone the repo

git clone --depth 1 https://github.com/navraj007in/architecture-cowork-plugin

Made for: Claude Code.

Or install architect, the plugin that ships this one along with the rest of its 48 skills, 63 commands, 19 agents, 7 MCP servers.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/check-env/github.svg)](https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/check-env)

Your own site

<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/check-env"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/navraj007in/architecture-cowork-plugin/check-env"><img src="https://agentmods.dev/badge/commands/navraj007in/architecture-cowork-plugin/check-env.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,608 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00016	$0.01608
Opus 5	$0.00008	$0.00804
Sonnet 5	$0.00003	$0.00322
Haiku 4.5	$0.00002	$0.00161

Measured 11d ago against content hash 9bb0637b03bb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade B, and why

check-env 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 11d 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.

- **Ubuntu/Debian**: `sudo apt install ...`

commands/check-env.md · 160 lines

How it starts

The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/architect:check-env

Trigger

/architect:check-env — run at any time to verify your local machine has the tools and runtimes needed for this project.

Purpose

Scan the SDL specification and project files to determine what tools, runtimes, databases, and credentials are needed for local development. Check which are installed and which are missing. Generate an actionable readiness report with install commands for each platform (macOS, Ubuntu, Windows).

Workflow

Step 1: Read Project Requirements

Read in this order:

architecture-output/_state.json — read first if it exists; provides compact tech_stack (frontend frameworks, backend frameworks, database, auth, deployment, integrations) and components (name, type, port, framework). Use these to identify required runtimes, tools, and credentials — skip reading the full SDL if _state.json covers the needed fields.
SDL file — only if _state.json is absent or lacks tech_stack/components; check solution.sdl.yaml first; if absent, read sdl/README.md then the relevant module files. Extract:
- Components — for each component, note the runtime, language, framework, and buildTool
- Data section — primaryDatabase, cache, queue, search — what data stores are needed
- Auth section — what auth provider is configured (may need specific CLIs)
- Deployment section — what cloud platform is targeted (may need specific CLIs)
- Infrastructure — Docker Compose, Kubernetes, Terraform requirements

Also check:

package.json → engines.node for required Node.js version
.python-version or pyproject.toml for Python version
go.mod for Go version
docker-compose.yml existence
.env.example for required credentials

Step 2: Check Each Requirement

For each identified requirement, run the appropriate check command:

Runtimes:

Runtime	Check Command	Version Parse
Node.js	`node --version`	`v22.x.x`
Python	`python3 --version`	`3.x.x`
Go	`go version`	`go1.x.x`
Rust	`rustc --version`	`1.x.x`
Java	`java --version`	`x.x.x`
.NET	`dotnet --version`	`x.x.x`
Ruby	`ruby --version`	`x.x.x`
PHP	`php --version`	`x.x.x`

Read the full file on GitHub · 160 lines

Changes

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.

11d ago First seen · 160 lines · 16 tokens per session scan B 9bb0637b03bb

Subscribe to this mod's changes

check-env is a command published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,608 once invoked, about $0.0001 per session on Opus 5. 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-31.

DevOps and cloud ai-agent architecture claude-code-plugin developer-tool scaffolding sdl

nyann:retrofit

Audit an existing repo against a profile and fix what's drifted. Unlike doctor (read-only), retrofit detects missing hooks, misconfigured gitignore, documentation gaps, and non-compliant history, then offers to remediate via bootstrap. Idempotent — safe to re-run.

thettwe/nyann · 61 tokens

nyann:apply

Apply an Infrastructure-as-Code change — the highest-stakes mutator in nyann; it can change real cloud infrastructure. Re-runs the plan, shows it, confirms, then applies. Unmistakably opt-in: apply is never the default and destructive applies require a second explicit confirm. For IaC apply intent only (not "apply a…

thettwe/nyann · 85 tokens

check-env