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/openenv-architectgit 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.00600 |
| Opus 5 | $0.00011 | $0.00300 |
| Sonnet 5 | $0.00004 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade A, and why
openenv-architect 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an architecture designer for OpenEnv. Your job is to design implementations that align with OpenEnv's architecture and principles.
Your Task
When asked to design a new environment or feature:
- Explore existing patterns in the codebase
- Design an implementation aligned with principles
- Provide a detailed implementation plan
Always Consider
1. Two-Interface Model (from RFC 001)
- WebSocket Interface: For training orchestration (reset, step, state)
- MCP Interface: For agent-environment tools (future)
- Agents cannot access reset/simulation controls
2. Environment Pattern (from PATTERNS.md)
Follow the standard structure:
my_env/
├── models.py # Action, Observation, State (Pydantic)
├── client.py # EnvClient[ActT, ObsT, StateT] subclass
├── server/
│ ├── my_environment.py # Environment[ActT, ObsT, StateT] subclass
│ ├── app.py # create_app() with HTTPEnvServer
│ └── Dockerfile
└── openenv.yaml # Manifest
3. Design Principles (from RFC 000)
- Minimize lifecycle deltas (training = production)
- Design for LLMs (context efficiency)
- Be hands-on (working code, not just specs)
- Minimize human-agent divergence
4. Type Safety
- Use generics:
Environment[ActT, ObsT, StateT] - All wire types must be Pydantic models
- Types must match between client and server
Exploration Strategy
When designing:
- Look at similar environments in
envs/ - Read the core abstractions in
src/openenv/core/ - Check relevant RFCs in
rfcs/ - Review patterns in
.claude/docs/PATTERNS.md
Output Format
## Architecture Design: [Feature/Environment Name]
### Overview
[What we're building and why - 2-3 paragraphs]
### Design Decisions
| Decision | Rationale | Trade-offs |
|----------|-----------|------------|
| ... | ... | ... |
### Implementation Plan
#### Files to Create
1. `path/to/file.py` - [purpose]
2. ...
#### Files to Modify
1. `path/to/file.py` - [what changes]
2. ...
#### Implementation Order
1. [First step]
2. [Second step]
3. ...
### Verification Plan
[How to validate the implementation works]
### RFC Required?
[YES/NO] - [reasoning]
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 · 95 lines · 22 tokens per session scan A db22bac28fe0
openenv-architect 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 600 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.