skillopt-sleep

A command runs or manages an agent's scheduled self-improvement cycle. The cycle reviews past sessions, repeats recurring tasks, and stores validated changes in memory and skill files.

In plain words
What is it for?
Use it to run, inspect, or schedule SkillOpt-Sleep with settings such as the model backend, preferences, or target skill path.
Why use it?
It provides one command for checking status, running the cycle, and controlling its options instead of manually starting each stage.

Command

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.

agentmods
npx agentmods add commands/microsoft/skillopt/skillopt-sleep
Clone the repo
git clone --depth 1 https://github.com/microsoft/SkillOpt
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,149 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00035 $0.01149
Opus 5 $0.00017 $0.00575
Sonnet 5 $0.00007 $0.00230
Haiku 4.5 $0.00003 $0.00115

Measured 2d ago against content hash 3f3504ca2d5e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

skillopt-sleep 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 2d 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.

plugins/claude-code/commands/skillopt-sleep.md · 86 lines

How it starts

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

/skillopt-sleep — SkillOpt-Sleep nightly self-evolution

You are driving SkillOpt-Sleep: a tool that lets this user's Claude agent improve from past usage by reviewing sessions, replaying recurring tasks, and consolidating what it learns into validated memory (CLAUDE.md) and skills (SKILL.md). With the default gate enabled, a change is kept only if it improves a held-out replay score. Nothing live is modified until adoption unless the user explicitly requests --auto-adopt.

Requested action: $ARGUMENTS

(If $ARGUMENTS is empty, treat it as status.)

How to run it

The engine is the skillopt_sleep Python package in this repo. Split $ARGUMENTS into the first action token and its remaining options, then use the plugin's bundled runner so the right interpreter and repo are on the path. Preserve the user's remaining options (for example --preferences, --backend, or --target-skill-path) instead of silently dropping them:

"${CLAUDE_PLUGIN_ROOT}/scripts/sleep.sh" <action> --project "$(pwd)" --scope invoked <remaining options>

<action> is one of:

action what it does
status show how many nights have run + the latest staged proposal (READ-ONLY)
dry-run harvest → mine → replay → report, but stage nothing (no-staging preview)
run full cycle: stage a validation report and any accepted proposal; only explicit --auto-adopt may also update live files
adopt apply the latest staged proposal to live CLAUDE.md / SKILL.md (backs up first)
harvest debug: print the recurring tasks mined from recent sessions
schedule install a nightly cron entry for this project (--hour --minute, off-:00 by default)
unschedule remove the nightly cron entry (--all to remove every managed entry)

Default backend is mock (deterministic, no API spend). To use real budget for model-driven optimization, add --backend claude or --backend codex. An accepted gain is evidence on this run's held-out tasks, not a guarantee of general improvement; results depend on the tasks, model, and checks. To steer what the optimizer writes, add --preferences "<your house rules>".

Read the full file on GitHub · 86 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. 2d ago First seen · 86 lines · 35 tokens per session scan A 3f3504ca2d5e

Subscribe to this mod's changes

skillopt-sleep is a command published in the GitHub repository microsoft/SkillOpt (16,489 stars, last pushed 2d ago), licensed MIT. It adds 35 tokens to every session and 1,149 once invoked, about $0.0002 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-30.