OpenEnv is a framework for creating, deploying, and using isolated execution environments through simple APIs modeled on Gymnasium. It is intended for researchers and developers training agents with reinforcement learning, as well as creators who need secure environments that can be deployed and accessed through familiar protocols. The catalogue add-ons provide agent integrations and workflows for using OpenEnv.
Borrowing it
Nothing to install: this file belongs to huggingface/OpenEnv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/huggingface/OpenEnv/main/.claude/skills/pre-submit-pr/SKILL.mdgit clone --depth 1 https://github.com/huggingface/OpenEnvWrote 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.
[](https://agentmods.dev/skills/huggingface/openenv/pre-submit-pr)<a href="https://agentmods.dev/skills/huggingface/openenv/pre-submit-pr"><img src="https://agentmods.dev/badge/skills/huggingface/openenv/pre-submit-pr/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/huggingface/openenv/pre-submit-pr"><img src="https://agentmods.dev/badge/skills/huggingface/openenv/pre-submit-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00048 | $0.00968 |
| Opus 5.5 | $0.00019 | $0.00387 |
| Sonnet 5.5 | $0.00010 | $0.00194 |
| Haiku 4.5 | $0.00005 | $0.00097 |
Grade A, and why
pre-submit-pr 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 1mo 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Submit PR Check
Comprehensive validation before submitting a pull request. Run this before creating or updating a PR.
Instructions
-
Check branch freshness (BLOCKING):
- Run
git fetch origin mainto get latest main - Run
git rev-list --count HEAD..origin/mainto check commits behind - If > 0 commits behind, merge main before proceeding:
git merge origin/main - This prevents "branch out of date" issues on GitHub
- Run
-
Run all automated hooks:
bash .claude/hooks/lint.sh- format check (includes ruff format + ruff check)bash .claude/hooks/test.sh- run testsbash .claude/hooks/check-debug.sh- find debug code
-
Run alignment review:
- Read
.claude/docs/PRINCIPLES.mdand.claude/docs/INVARIANTS.md - Compare changes against principles and invariants
- Identify Tier 1 (mechanical) and Tier 2 (alignment) issues
- Read
-
RFC check:
- If changes touch
src/openenv/core/, flag for RFC consideration - If any public API signatures change, RFC required
- Check against existing RFCs in
rfcs/for conflicts
- If changes touch
-
Documentation freshness check:
- Review
.claude/docs/REPO_WALKTHROUGH.mdagainst the current repo structure - If the PR adds new directories, moves files, or changes structure significantly:
- Update REPO_WALKTHROUGH.md to reflect the changes
- Include these updates in the PR
- Check triggers: new directories in
src/,envs/,.claude/, orrfcs/ - Check if any public API signatures changed (function/class renames, new params):
- Search for references in docs/, examples/, README.md, other .py docstrings
- If stale references found, recommend running
/update-docsbefore PR
- Review
-
Summarize PR readiness:
- List all blocking issues
- List all discussion points for reviewers
- Provide overall verdict
-
After push/PR creation, run the post-push check:
bash .claude/hooks/post-push-pr.sh- Verifies: PR is open, no merge conflicts, branch freshness, PR description quality, CI check status
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.
- 1mo ago First seen · 112 lines · 48 tokens per session scan A c58757ea231e
pre-submit-pr is a skill published in the GitHub repository huggingface/OpenEnv (2,739 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 48 tokens to every session and 968 once invoked, about $0.0002 per session on Opus 5.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 skills, from other repositories
pr
Draft a PR body from OMC's paper trail — the smallest visual that proves the change, evidence consumed from the verify protocol (never re-collected), reversibility from the ADR test on the diff, glossary language throughout.
merge-batch
Prepare and merge an owner-selected PR batch with contributor credit and exact-candidate admission. Use for a pasted PR list; combined focused validation is diagnostic, and every actual landing still requires its applicable checks and authorization.
otto-pr-review-loop
Run Polly and OCR on a PR until all findings settle.
engram-branch-pr
PR creation workflow for Engram following the issue-first enforcement system. Trigger: When creating a pull request, opening a PR, or preparing changes for review.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
revdiff
Review diffs, files, and documents with inline annotations in a TUI overlay, or answer questions about revdiff usage, configuration, themes, and keybindings. Opens revdiff in agterm/tmux/zellij/herdr/kitty/wezterm/cmux/ghostty/iterm2/emacs-vterm, captures annotations, and addresses them. Works in git, hg, and jj repos…