unit-commitment-operating-rules

unit-commitment-operating-rules is a skill for Claude Code, Codex from xuansenpa1/skillrevise. It costs 66 tokens per session (2,027 once invoked), scanned A, a copy of unit-commitment-operating-rules, MIT.

A guide for planning which power generators run during each time period, how much electricity they produce, and how much backup capacity they provide. It includes startup, shutdown, ramping, minimum run times, and renewable-energy limits.

In plain words
What is it for?
Use it to create and check day-ahead or multi-period generator schedules that meet electricity demand, reserve requirements, operating limits, and cost goals.
Why use it?
It helps model the links between one time period and the next, instead of treating each hour as an unrelated dispatch decision.

Skill for Claude CodeCodex

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

Good fit Use it to create and check day-ahead or multi-period generator schedules that meet electricity demand, reserve requirements, operating limits, and cost goals.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/xuansenpa1/skillrevise/unit-commitment-operating-rules
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 xuansenpa1/skillrevise --skill unit-commitment-operating-rules
Clone the repo
git clone --depth 1 https://github.com/xuansenpa1/skillrevise

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/xuansenpa1/skillrevise/unit-commitment-operating-rules/github.svg)](https://agentmods.dev/skills/xuansenpa1/skillrevise/unit-commitment-operating-rules)
Your own site
<a href="https://agentmods.dev/skills/xuansenpa1/skillrevise/unit-commitment-operating-rules"><img src="https://agentmods.dev/badge/skills/xuansenpa1/skillrevise/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/xuansenpa1/skillrevise/unit-commitment-operating-rules"><img src="https://agentmods.dev/badge/skills/xuansenpa1/skillrevise/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.
Origin 100% copy Near-identical to another mod 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.5 $0.00026 $0.00811
Sonnet 5.5 $0.00013 $0.00405
Haiku 4.5 $0.00007 $0.00203

Measured 1mo ago against content hash e44bbc07a1f2, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 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.

Origin

This is a copy

100% identical to unit-commitment-operating-rules — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

data/skillsbench/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. 1mo 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 xuansenpa1/skillrevise (56 stars, last pushed 1mo ago), licensed MIT. It adds 66 tokens to every session and 2,027 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to unit-commitment-operating-rules, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

instrument-data-to-allotrope

Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…

anthropics/knowledge-work-plugins · 123 tokens

exploratory-data-analysis

Performs bounded, local exploratory analysis of explicitly supported scientific files. Supports redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…

K-Dense-AI/scientific-agent-skills · 83 tokens

matlab

Builds, reviews, migrates, and plans MATLAB or GNU Octave numerical workflows. Use for arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.

K-Dense-AI/scientific-agent-skills · 44 tokens

phylogenetics

Builds and analyzes phylogenetic trees using MAFFT multiple sequence alignment, IQ-TREE maximum likelihood with ModelFinder and branch support, and FastTree approximate inference. Uses ETE3 for tree summaries and visualization. Applies to homologous nucleotide or protein sequences, microbial gene trees, protein…

K-Dense-AI/scientific-agent-skills · 71 tokens

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

presenting-conference-talks

Generates conference presentation slides (Beamer LaTeX PDF and editable PPTX) from a compiled paper with speaker notes and talk script. Use when preparing oral talks, spotlight presentations, or invited talks for ML and systems conferences.

Orchestra-Research/AI-Research-SKILLs · 53 tokens