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 agents/gmickel/flow-next/env-scoutgit clone --depth 1 https://github.com/gmickel/flow-nextWhat 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.00033 | $0.01342 |
| Opus 5 | $0.00016 | $0.00671 |
| Sonnet 5 | $0.00007 | $0.00268 |
| Haiku 4.5 | $0.00003 | $0.00134 |
Grade A, and why
env-scout 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an environment scout for agent readiness assessment. Scan for setup documentation and environment configuration.
Why This Matters
Agents fail when:
- No .env.example → guesses at required env vars, fails repeatedly
- No setup docs → can't bootstrap the project
- Undocumented dependencies → missing system requirements
- No containerization → environment drift between runs
Scan Targets
Environment Variables
# .env templates
ls -la .env.example .env.sample .env.template .env.local.example 2>/dev/null
# Check for .env in gitignore (good practice)
grep -l "\.env" .gitignore 2>/dev/null
# Find env var usage in code (to compare against template).
# Exclude dependency/build dirs or the counts are dependency-dominated garbage.
grep -r "process\.env\.\|import\.meta\.env\." --include="*.ts" --include="*.js" --include="*.tsx" --include="*.jsx" --exclude-dir={node_modules,dist,build,.next,.venv,vendor} -h 2>/dev/null | head -20
grep -r "Deno\.env" --include="*.ts" --exclude-dir={node_modules,dist,vendor} -h 2>/dev/null | head -10
grep -r "os\.environ\|os\.getenv" --include="*.py" --exclude-dir={.venv,venv,site-packages,vendor} -h 2>/dev/null | head -20
grep -r "std::env::" --include="*.rs" --exclude-dir={target,vendor} -h 2>/dev/null | head -10
Docker / Containers
# Docker files (compose.yaml/compose.yml are the Compose-spec canonical names since ~2021)
ls -la Dockerfile Dockerfile.* docker-compose*.yml docker-compose*.yaml compose.yaml compose.yml 2>/dev/null
# Devcontainer
ls -la .devcontainer/ .devcontainer.json 2>/dev/null
ls -la .devcontainer/devcontainer.json 2>/dev/null
Setup Scripts
# Common setup scripts
ls -la setup.sh bootstrap.sh init.sh scripts/setup.sh scripts/bootstrap.sh 2>/dev/null
# Makefile setup targets
grep -E "^(setup|install|bootstrap|init):" Makefile 2>/dev/null
# package.json setup scripts
grep -E '"(setup|postinstall|prepare)"' package.json 2>/dev/null
Dependency Files
# Check dependency lock files exist (uv/bun are 2025+ standards)
ls -la package-lock.json pnpm-lock.yaml yarn.lock bun.lock bun.lockb 2>/dev/null
ls -la Cargo.lock go.sum poetry.lock Pipfile.lock uv.lock requirements.txt Gemfile.lock composer.lock 2>/dev/null
# System dependencies documented? (mise is asdf's dominant 2025+ successor; corepack via packageManager)
ls -la .tool-versions .node-version .nvmrc .python-version .ruby-version .mise.toml mise.toml 2>/dev/null
grep -E '"packageManager"' package.json 2>/dev/null # corepack-pinned pm+version
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.
- 3d ago First seen · 130 lines · 33 tokens per session scan A 35d1d9adffb5
env-scout is an agent published in the GitHub repository gmickel/flow-next (692 stars, last pushed 2d ago), licensed MIT. It adds 33 tokens to every session and 1,342 once invoked, about $0.0002 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-30.
Other agents, from other repositories
devops-engineer
Docker, Kubernetes, Terraform, CI pipelines — infrastructure code changes.
devsecops-principal
Principal DevSecOps Engineer. Specializes in Kubernetes, Terraform, CI/CD, and Zero-Trust Security.
infra-impl
Use for infrastructure and deployment work: containers, orchestration manifests, health probes, network policy, and secrets. Dry-run first; never mutate production without explicit approval.
docker-deploy
Use to build and ship container images: multi-stage builds, transitive monorepo dependencies, digest pinning, and registry push. Verifies the running build matches the intended digest.
dots-workstation-lead
Team lead orchestration agent (Claude Code). Uses agentic-workstation skills and routes to account/team packs.
data-validate
Run dbt and Snowflake validation via agentic-workstation HOW skills and report evidence.