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.
npx skills add ReinaMacCredy/maestro --skill maestro-bundlegit clone --depth 1 https://github.com/ReinaMacCredy/maestroWrote 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.
[](https://agentmods.dev/skills/reinamaccredy/maestro/maestro-bundle)<a href="https://agentmods.dev/skills/reinamaccredy/maestro/maestro-bundle"><img src="https://agentmods.dev/badge/skills/reinamaccredy/maestro/maestro-bundle/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.
<a href="https://agentmods.dev/skills/reinamaccredy/maestro/maestro-bundle"><img src="https://agentmods.dev/badge/skills/reinamaccredy/maestro/maestro-bundle.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00032 | $0.01195 |
| Opus 5.5 | $0.00013 | $0.00478 |
| Sonnet 5.5 | $0.00006 | $0.00239 |
| Haiku 4.5 | $0.00003 | $0.00120 |
Grade A, and why
maestro-bundle 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
maestro-bundle
Use WORKFLOW.md for method rules and routing. This skill owns record creation, resume, and handoff procedures.
Tier rule
Apply Tiers after bounded reconnaissance.
For tracked work use maestro work add|start|done. When Full is warranted,
open the bundle in the store whose checkout will change, even when design
runs in the Hub. List Hub decisions as hub:<id>; maestro bundle show
renders them. Note the bundle on the Hub map and the map on its work item.
maestro bundle open <id> --work <workId> # scaffold SPEC/NOTES/VERIFY, link work
The trio contract
Follow Bundle contract.
Use maestro handoff <bundle-id> to render NOTES.md from work, decisions,
handbacks, failures, and the latest checkpoint. Fill only placeholders the
store cannot prove, including original authorization and retained gates.
Use maestro bundle show <id> to read the contract and linked decisions.
Never create root SPEC-*, NOTES-*, or VERIFY-* files.
Verbs
maestro bundle open <id> [--work <id>] # scaffold + active row
maestro bundle close <id> # snapshot trio into the store, archive
maestro bundle pause <id> [--reason] # active stays open, out of the way
maestro bundle resume <id> # paused back to active
maestro bundle list # states: active | paused | archived
maestro bundle show <id> # trio + linked work + decisions
maestro bundle save <dir> # ingest a foreign trio dir as archived
maestro search "<term>" # recall: hits labeled (bundle, ...)
Authorization boundaries
Follow Authorization boundaries. Put the original user instruction or retrievable reference on the work item so the successor can verify the grant, rather than relying on an agent's summary.
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.
- 8d ago Changed 0f1a984f298a
- 1mo ago Changed · -65 lines 0a6dc7d539ce
- 1mo ago Changed · +6 lines ecc1fb16e83c
- 1mo ago Changed · +86 lines 05b5d42042e3
- 1mo ago First seen · 90 lines · 32 tokens per session scan A ffc9ca994062
maestro-bundle is a skill published in the GitHub repository ReinaMacCredy/maestro (235 stars, last pushed 9d ago), licensed MIT. It adds 32 tokens to every session and 1,195 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-30.
Other skills, from other repositories
pn-session-handoff
End a session with a structured handoff document and two reflection questions. Captures shipped work, dangling state, resume action, and blind spots. Use via /pn-handoff before closing a session. Pairs with pn-continual-learning for AGENTS.md updates.
pn-context-engineering
Choose which rules, specs, and files to load this turn. Use when context is bloated, the agent ignores conventions, or you are switching tasks — not for a single-file edit with a clear path.
google-apps-script
Google Apps Script development for automating Google Workspace - Sheets, Docs, Gmail, Drive, Calendar and Forms - with built-in services, triggers and the appsscript.json manifest. Use when writing or fixing a .gs file, automating a Google Sheet, sending or processing Gmail from a script, setting up time-based or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
generate-run-commands
Generate or modify run commands for the current session. Use when the user wants to set up or update run commands that appear in the session's Run button.
debugging-executions
Debug failed or wrong-output workflow executions using executions tools. Load when the user reports execution failures, unexpected node output, empty parameter values after a successful run, or a node showing a red or failed expression error. Also load when a live run you started for the user fails with an error from…