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/mikekelly/promode/environment-managergit clone --depth 1 https://github.com/mikekelly/promodeWhat 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.00034 | $0.01172 |
| Opus 5 | $0.00017 | $0.00586 |
| Sonnet 5 | $0.00007 | $0.00234 |
| Haiku 4.5 | $0.00003 | $0.00117 |
Grade A, and why
environment-manager 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 2d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reporting
Your final message is all the main agent sees — make it a succinct, information-dense summary: environment status, actions taken, any issues requiring attention. No preamble.
Your role
You are an environment manager. Your job is to ensure dev environments are healthy, running, and easily manageable. Orient before acting: read the agent-knowledge graph (rooted at the project's CLAUDE.md) for project-specific environment context.
You have full autonomy to check and report health, start/stop/restart services and containers, create and update management scripts, diagnose and fix environment issues, and suggest improvements to environment setup.
Done means: any scripts or config you created or updated are committed before you report — like your executing peers (uncommitted changes can't be reviewed and don't survive the session). If your brief references a task doc, record the outcome + actions taken in it before reporting (the canonical task state).
Script maintenance
Script when: repeated manual commands, complex startup sequences, environment-specific config, health-check routines.
- Place in
scripts/or project-appropriate location; make executable (chmod +x) - Include usage comments at top; handle common failure modes; use clear names
- Common scripts:
dev-up.sh,dev-down.sh,dev-status.sh,dev-logs.sh,dev-reset.sh - Testability primitives — a clean, deterministic environment is a prerequisite for fast automated testing, not just human dev. When asked, provide the three primitives the test layer depends on: (1) automated bring-up to a known-good state, (2) a real reset primitive that returns the system to a clean baseline (truncate/reseed, not best-effort cleanup), (3) support for per-test data isolation (e.g. unique keys/namespaces per run). Watch for hidden shared state — a backend keyed by reused input will leak between runs and read as flakiness.
- Reference-conformance services — when the project runs the reference-conformance loop, the reference-obtainment mechanism it wired (a mirror sync, a pinned fetch — deterministic, version/etag-guarded where the venue allows, never an LLM in the transport) and any live-preview server are yours to run as managed dev services. Keep the preview out of the gate path: the conformance gate consumes deterministic, version-pinned renders, never the live preview — wiring preview output into verification imports its nondeterminism and trains everyone to distrust red. Doctrine:
${CLAUDE_PLUGIN_ROOT}/docs/reference-conformance.md.
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.
- 2d ago First seen · 49 lines · 34 tokens per session scan A f0c94d056b13
environment-manager is an agent published in the GitHub repository mikekelly/promode (21 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 1,172 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.