OpenEnv: Skill for Claude Code

.claude/skills/rfc-check/SKILL.md

rfc-check is a skill for Claude Code from huggingface/OpenEnv. It costs 32 tokens per session (514 once invoked), scanned A, original, BSD-3-Clause.

A checklist for deciding whether a proposed OpenEnv change needs an RFC, a written design proposal reviewed before major work begins.

In plain words
What is it for?
Use it during planning to inspect changed files, public API changes, new design patterns, and related RFCs, then report whether an RFC is required.
Why use it?
It distinguishes routine fixes and documentation work from changes that could alter public interfaces, architecture, or the separation between training and agent access.

Skill for Claude Code ✓ vendor

Written for Claude Code: allowed-tools in frontmatter.

This is huggingface/OpenEnv's own configuration. It tells Claude Code how to work on OpenEnv itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything OpenEnv configures →

About the project

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.

huggingface/OpenEnv · 2,739 stars · on GitHub · huggingface.co

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/huggingface/OpenEnv/main/.claude/skills/rfc-check/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/huggingface/OpenEnv

Made for: Claude Code.

Wrote 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.

agentmods badge for rfc-check

README.md
[![agentmods](https://agentmods.dev/badge/skills/huggingface/openenv/rfc-check/github.svg)](https://agentmods.dev/skills/huggingface/openenv/rfc-check)
Your own site
<a href="https://agentmods.dev/skills/huggingface/openenv/rfc-check"><img src="https://agentmods.dev/badge/skills/huggingface/openenv/rfc-check/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.

agentmods 80×15 button for rfc-check

Your own site · 80×15
<a href="https://agentmods.dev/skills/huggingface/openenv/rfc-check"><img src="https://agentmods.dev/badge/skills/huggingface/openenv/rfc-check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 32 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 514 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00032 $0.00514
Opus 5.5 $0.00013 $0.00206
Sonnet 5.5 $0.00006 $0.00103
Haiku 4.5 $0.00003 $0.00051

Measured 1mo ago against content hash 33e90598433b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

rfc-check 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.

.claude/skills/rfc-check/SKILL.md · 93 lines

What it actually says

RFC Check

Determine if proposed changes require an RFC (Request for Comments).

Instructions

  1. Identify changed files using git diff --name-only or provided context

  2. Apply RFC criteria:

    RFC Required:

    • New APIs in src/openenv/core/
    • Breaking changes to existing APIs
    • New abstractions or design patterns
    • Changes affecting the two-interface model (WebSocket/MCP separation)
    • Major architectural decisions

    RFC Not Required:

    • Bug fixes
    • Documentation updates
    • Minor refactoring (no API changes)
    • New example environments (unless introducing new patterns)
    • Dependency updates
    • Test additions
  3. Check against existing RFCs in rfcs/ for conflicts or dependencies

Analysis Steps

  1. List all files being changed
  2. Identify any files in src/openenv/core/
  3. Check for public API signature changes
  4. Look for new abstractions or patterns
  5. Review existing RFCs for related decisions

Output Format

## RFC Analysis

### Files Changed
- [list of files]

### Core Files Touched
- [any files in src/openenv/core/, or "None"]

### API Changes
- [any signature changes to public APIs, or "None"]

### New Patterns/Abstractions
- [any new patterns introduced, or "None"]

### Verdict: NOT REQUIRED / RECOMMENDED / REQUIRED

### Reasoning
[Explanation of decision based on criteria above]

### If RFC Needed
- Suggested title: "RFC NNN: [title]"
- Related RFCs: [list any related existing RFCs]
- Key decisions to document: [list]

RFC Template Reference

If an RFC is needed, use the template in rfcs/README.md:

# RFC NNN: Title

**Status**: Draft
**Created**: YYYY-MM-DD
**Authors**: @username

## Summary
[1-2 paragraph overview]

## Motivation
[Problem Statement + Goals]

## Design
[Architecture Overview, Core Abstractions, Key Design Decisions]

## Examples
[Code samples demonstrating usage]
Changes

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.

  1. 1mo ago First seen · 93 lines · 32 tokens per session scan A 33e90598433b

Subscribe to this mod's changes

rfc-check is a skill published in the GitHub repository huggingface/OpenEnv (2,739 stars, last pushed 8d ago), licensed BSD-3-Clause. It adds 32 tokens to every session and 514 once invoked, about $0.0001 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.

Related

Other skills, from other repositories

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens