maestro-improve

maestro-improve is a skill for Claude Code, Codex from ReinaMacCredy/maestro. It costs 54 tokens per session (2,892 once invoked), scanned A, original, MIT.

A maintenance workflow that turns recorded lessons into small, evidence-backed edits to project instructions or other local guidance. It groups lessons by the rule or document they affect and records which commit processed each one.

In plain words
What is it for?
Use it when the Maestro process reports lessons that need to be incorporated into a recipe, room rule, skill file, template, or repository workspace protocol.
Why use it?
Corrections mentioned only in a conversation disappear when the session ends. This workflow puts accepted lessons into the instructions that future sessions will read, while keeping one focused change per target.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions subagents.

Good fit Use it when the Maestro process reports lessons that need to be incorporated into a recipe, room rule, skill file, template, or repository workspace protocol.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/reinamaccredy/maestro/maestro-improve
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 ReinaMacCredy/maestro --skill maestro-improve
Clone the repo
git clone --depth 1 https://github.com/ReinaMacCredy/maestro

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 maestro-improve

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/reinamaccredy/maestro/maestro-improve"><img src="https://agentmods.dev/badge/skills/reinamaccredy/maestro/maestro-improve.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,892 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.00054 $0.02892
Opus 5.5 $0.00022 $0.01157
Sonnet 5.5 $0.00011 $0.00578
Haiku 4.5 $0.00005 $0.00289

Measured 8d ago against content hash 9605df7bbf2c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

maestro-improve 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.

src/plugins/skills/maestro-improve/SKILL.md · 237 lines

How it starts

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

maestro-improve

Use when a Lead assigns improvement work on one target to a Peer. The target is the only parameter; a separate Peer challenges the returned candidate before acceptance.

A correction that stays in a transcript is spent when that session ends. The lesson record is what survives, and doctrine is the only thing a future session actually reads. This skill is the one place the two are joined: it turns filed corrections into the smallest edit that would have prevented them.

Folds rules from pstack's reflect and correct (Lauren Tan, MIT; notice in THIRD_PARTY.md).

The parameter

The target names the doctrine a lesson corrects: a recipe section, the SLP Workspace Pack in src/plugins/resources/SLP.md, a Hub template, a skills/maestro-* file, or a repository's Workspace Protocol. Where each one lives, and what an edit to it costs, is in references/targets.md.

Intakes

Most lessons are filed at the correction, by the seat that took it. Two intakes catch the ones nobody filed. Both end in maestro lesson file, and neither edits doctrine. Filing is reversible, so it waits for no approval; the edit a lesson later produces passes the replay gate and the challenge Peer like any other.

Session harvest. Run it after a session whose corrections nobody marked. Skip a trivial session, or one that followed its doctrine correctly. A one-off is not a lesson. The source is the session's record, not a transcript file. That record is maestro trace <id> for each work item the session touched, its failed: notes, its rework marks, the decisions it recorded with --replaces, and a short digest of the conversation written by the session itself. Hand the record to three read-only subagents in parallel, one lens each:

  • Judgment. The durable principle behind a specific incident: a mistake and its correction, an owner preference, a decision and its reason, friction in a skill or a delegation, a manual step repeated often enough to encode.
  • Tooling. The command, flag, path or quirk a future agent would otherwise re-derive, and every moment the owner supplied context the agent could have fetched itself.
  • Divergent. What the other two lenses will miss: a decision right for the wrong reason, a check reported instead of run, a second-order effect on callers, a skill invoked late or not at all.

Read the full file on GitHub · 237 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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 Changed · +91 lines 9605df7bbf2c
  2. 27d ago Changed · +32 lines 1ce8b1b0a84e
  3. 1mo ago Changed · +54 tokens per session 82f7a83fe0ec
  4. 1mo ago Changed · +6 lines · -54 tokens per session a00237e3d162
  5. 1mo ago First seen · 108 lines · 54 tokens per session scan A f6f8a1a70239

Subscribe to this mod's changes

maestro-improve is a skill published in the GitHub repository ReinaMacCredy/maestro (235 stars, last pushed 9d ago), licensed MIT. It adds 54 tokens to every session and 2,892 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-30.