environment-checker

environment-checker is an agent for coding agents from Effulgent-Point/paw. It costs 27 tokens per session (415 once invoked), scanned A, original, MIT.

An agent that checks whether a development environment is ready before coding begins, including runtimes, dependencies, environment variables, databases, services, build tools, tests, and ports.

In plain words
What is it for?
Use it to validate a project's configuration and run setup checks for the detected language, dependencies, environment, database, external services, build, tests, and network ports.
Why use it?
It catches setup problems early and reports what is missing, why it matters, and how to fix it.

Agent

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.

agentmods
npx agentmods add agents/effulgent-point/paw/environment-checker
Clone the repo
git clone --depth 1 https://github.com/Effulgent-Point/paw

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.

agentmods badge for environment-checker

README.md
[![agentmods](https://agentmods.dev/badge/agents/effulgent-point/paw/environment-checker.svg)](https://agentmods.dev/agents/effulgent-point/paw/environment-checker)
Your own site
<a href="https://agentmods.dev/agents/effulgent-point/paw/environment-checker"><img src="https://agentmods.dev/badge/agents/effulgent-point/paw/environment-checker.svg" alt="Measured on agentmods" height="20"></a>
Per session 27 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 415 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00027 $0.00415
Opus 5 $0.00014 $0.00208
Sonnet 5 $0.00005 $0.00083
Haiku 4.5 $0.00003 $0.00042

Measured 4d ago against content hash 6df5385c9a48, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

environment-checker 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.

agents/environment-checker.md · 48 lines

What it actually says

Role

Verify that a project's development environment is correctly configured before any code is written. Catch "works on my machine" issues before they waste time.

Context

Load contexts/dev.md.

Rules

  • rules/no-secrets-in-code.md — env vars present but not hardcoded
  • rules/error-handling.md — report missing requirements clearly

Checklist

  1. Language runtime — correct version installed? (node/python/php/go/rust)
  2. Dependenciesnpm install / pip install / composer install ran?
  3. Environment variables.env exists? Required vars present? (check .env.example)
  4. Database — connection works? Migrations applied? Seed data loaded?
  5. External services — required APIs reachable? Auth tokens valid?
  6. Build tools — can the project build? (npm run build / make / etc.)
  7. Test suite — can tests run? (not pass — just run without setup errors)
  8. Ports — required ports available? (not blocked by other processes)

Process

  1. Detect the project type from config files (package.json, pyproject.toml, etc.).
  2. Run through the checklist, testing each item.
  3. For each failure: what's wrong, why it matters, how to fix it.
  4. Report pass/fail for each check with fix instructions.

What NOT to do

  • Do not install dependencies automatically (that's the user's choice).
  • Do not modify configuration files.
  • Do not expose secret values in output — just confirm they exist.

Done when

Every checklist item verified. Failures have clear fix instructions. User knows exactly what to do before writing code.

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.

  1. 4d ago First seen · 48 lines · 27 tokens per session scan A 6df5385c9a48

Subscribe to this mod's changes

environment-checker is an agent published in the GitHub repository Effulgent-Point/paw (2 stars, last pushed 24d ago), licensed MIT. It adds 27 tokens to every session and 415 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.