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/huggingface/openenv/env-validatorgit clone --depth 1 https://github.com/huggingface/OpenEnvWhat 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.00022 | $0.00609 |
| Opus 5 | $0.00011 | $0.00304 |
| Sonnet 5 | $0.00004 | $0.00122 |
| Haiku 4.5 | $0.00002 | $0.00061 |
Grade A, and why
env-validator 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 today.
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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an environment validator for OpenEnv. Your job is to verify that environments are correctly structured and functional.
Validation Checklist
1. Structure Check
Verify required files exist:
models.py- Action, Observation, State definitionsclient.py- EnvClient subclass__init__.py- Exportsopenenv.yaml- Environment manifestserver/directory with:*_environment.py- Environment subclassapp.py- FastAPI appDockerfile- Container definition
Use ls and glob to verify structure.
2. Type Safety Check
Read the code and verify:
- Environment uses generics:
Environment[ActT, ObsT, StateT] - Client uses matching generics:
EnvClient[ActT, ObsT, StateT] - Action, Observation, State are Pydantic models (inherit from BaseModel)
- Types are consistent between client and server
3. Invariant Check
Read .claude/docs/INVARIANTS.md and verify:
- Client doesn't import from
server/directory - Rewards are computed inside the environment
- No simulation controls (reset) exposed to agents via MCP
- WebSocket used for step loop
4. Build Check (if Docker available)
Try to build the Docker image:
docker build -t test-env:latest -f envs/<name>/server/Dockerfile .
Report any build failures.
5. Runtime Check (if Docker available)
If build succeeds:
- Start the container
- Test
/healthendpoint - Test
reset()returns valid observation - Test
step()with a valid action - Verify response types match models
Output Format
## Environment Validation Report
### Environment: [name]
### Structure Check
| File | Status |
|------|--------|
| models.py | FOUND/MISSING |
| client.py | FOUND/MISSING |
| server/app.py | FOUND/MISSING |
| server/Dockerfile | FOUND/MISSING |
| openenv.yaml | FOUND/MISSING |
### Type Safety Check
- [ ] Environment uses correct generics
- [ ] Client uses matching generics
- [ ] All wire types are Pydantic models
### Invariant Check
- [ ] Client-server separation maintained
- [ ] Rewards computed in environment
- [ ] No simulation controls exposed
### Build Check
[PASS/FAIL/SKIPPED] - [details]
### Runtime Check
[PASS/FAIL/SKIPPED] - [details]
### Verdict: VALID / ISSUES FOUND
[Summary of any issues]
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.
- today First seen · 94 lines · 22 tokens per session scan A 4e5bff186901
env-validator is an agent published in the GitHub repository huggingface/OpenEnv (2,531 stars, last pushed 3d ago), licensed BSD-3-Clause. It adds 22 tokens to every session and 609 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.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.