unit-commitment-operating-rules

unit-commitment-operating-rules is a skill for Claude Code, Codex from benchflow-ai/skillsbench. It costs 66 tokens per session (2,027 once invoked), scanned A, original, Apache-2.0.

A guide to unit commitment, the process of deciding which power generators run during each time period, how much they produce, and when they start or stop. It accounts for operating limits, reserves, and time-dependent rules.

In plain words
What is it for?
Use it to build and check day-ahead generator schedules and multi-period power-system operating plans.
Why use it?
It keeps related generator decisions consistent across hours, including minimum run times, ramping, startup costs, and reserve availability.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to build and check day-ahead generator schedules and multi-period power-system operating plans.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/benchflow-ai/skillsbench/unit-commitment-operating-rules
About the project

SkillsBench is a benchmark for measuring how effectively AI agents use modular skills—folders containing instructions, scripts, and resources—to complete specialized tasks. It helps researchers and developers evaluate both skill quality and agent behavior, including tasks that require combining multiple skills. The catalogue’s skills and instructions are evaluated as part of this workflow.

benchflow-ai/skillsbench · 1,764 stars · on GitHub · skillsbench.ai

Install

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.

Any agent
npx skills add benchflow-ai/skillsbench --skill unit-commitment-operating-rules
Clone the repo
git clone --depth 1 https://github.com/benchflow-ai/skillsbench

Made for: Claude Code, Codex.

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 unit-commitment-operating-rules

README.md
[![agentmods](https://agentmods.dev/badge/skills/benchflow-ai/skillsbench/unit-commitment-operating-rules/github.svg)](https://agentmods.dev/skills/benchflow-ai/skillsbench/unit-commitment-operating-rules)
Your own site
<a href="https://agentmods.dev/skills/benchflow-ai/skillsbench/unit-commitment-operating-rules"><img src="https://agentmods.dev/badge/skills/benchflow-ai/skillsbench/unit-commitment-operating-rules/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 unit-commitment-operating-rules

Your own site · 80×15
<a href="https://agentmods.dev/skills/benchflow-ai/skillsbench/unit-commitment-operating-rules"><img src="https://agentmods.dev/badge/skills/benchflow-ai/skillsbench/unit-commitment-operating-rules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 66 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,027 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.00066 $0.02027
Opus 5 $0.00033 $0.01014
Sonnet 5 $0.00013 $0.00405
Haiku 4.5 $0.00007 $0.00203

Measured 8d ago against content hash e44bbc07a1f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

unit-commitment-operating-rules 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 8d 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

tasks/energy-unit-commitment/environment/skills/unit-commitment-operating-rules/SKILL.md · 241 lines

How it starts

The opening of the file, as written. The whole thing — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Unit Commitment Operating Rules

Use this skill when a task asks for a day-ahead or multi-period unit commitment schedule with generators, load, reserves, operating constraints, and cost tradeoffs.

This is a reusable UC operating guide. It gives formulation and validation patterns, not a complete task-specific mathematical model.

UC In One Paragraph

Unit commitment decides which generators are online over time, when they start or stop, how much they produce, and how much reserve they can physically provide. It is harder than hourly economic dispatch because startup/shutdown decisions, ramping, minimum up/down time, reserve deliverability, initial conditions, and cost curves couple one period to the next.

Keep These Concepts Separate

For each thermal unit g and period t:

u[g, t]      # commitment/on status, binary
start[g, t]  # startup transition, binary
stop[g, t]   # shutdown transition, binary
p[g, t]      # production variable: know whether actual MW or above-minimum MW
r[g, t]      # scheduled reserve

Reports often require actual MW output. Many UC models internally use output above minimum:

actual_output = pmin[g] * u[g, t] + p_above_min[g, t]
p_above_min = actual_output - pmin[g] * u[g, t]

Do not mix these conventions in ramping, reserve, cost, or reporting.

Core Feasibility Checks

Before reporting a schedule, independently verify:

  • every resource appears exactly once and all time-series have length T;
  • commitment, startup, and shutdown are binary;
  • offline thermal units have zero production and zero reserve;
  • online thermal units respect min/max output;
  • must-run units are online when required;
  • startup/shutdown indicators match commitment transitions;
  • demand balance holds in every period;
  • renewable output stays within period-specific bounds;
  • scheduled reserve meets the system requirement;
  • reserve is deliverable under headroom, startup/shutdown capability, and ramp limits;
  • minimum up/down time and initial conditions are respected;
  • cost and summary fields are recomputed from arrays.

Read the full file on GitHub · 241 lines

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. 8d ago First seen · 241 lines · 66 tokens per session scan A e44bbc07a1f2

Subscribe to this mod's changes

unit-commitment-operating-rules is a skill published in the GitHub repository benchflow-ai/skillsbench (1,764 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 66 tokens to every session and 2,027 once invoked, about $0.0003 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-09-03.