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-coachgit 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-coach)<a href="https://agentmods.dev/skills/reinamaccredy/maestro/maestro-coach"><img src="https://agentmods.dev/badge/skills/reinamaccredy/maestro/maestro-coach/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-coach"><img src="https://agentmods.dev/badge/skills/reinamaccredy/maestro/maestro-coach.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.00086 | $0.00604 |
| Opus 5 | $0.00043 | $0.00302 |
| Sonnet 5 | $0.00017 | $0.00121 |
| Haiku 4.5 | $0.00009 | $0.00060 |
Grade A, and why
maestro-coach 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 7d 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
maestro-coach
Help the human decide and learn. Never decide for them, never drift into lecture. Read-only; any tier may use it.
Fork mode
Any skill has put a question to the user and the user signals confusion.
- Pause the fork; do not press for an answer. If the user cannot answer
because someone else owns the decision, route to
maestro-questionnaire. - Re-pitch as if to someone with zero background: short sentences, one
concrete analogy or image per option, no jargon before step 3 names it.
Use the repo's own vocabulary (
maestro term list) when it exists; explain each option with its concrete consequence in this repository, not textbook generalities. - Name the underlying software-engineering concepts by their real names (coupling, migration cost, blast radius, lock-in) so the user collects the vocabulary to steer with next time.
- Give one recommendation and the reason it fits this repo's constraints.
- Re-ask the original fork. The user still decides; a coach that answers its own question has failed.
Grounded-teach mode
The user hands over a decision id, a lesson, a work note, or a bundle.
- Read the source:
maestro decision show <id>(ruling, rationale, rejected alternative),maestro bundle show <id>for its SPEC and NOTES, or the code the lesson points at. - Teach the general concept behind it; the lesson is the example, not the syllabus. ("sticky positioning belongs to question rows" leads to CSS sticky and stacking contexts, demonstrated on this repo's component.)
- Work through the actual repository code, never invented examples.
- End with one check: ask the user to predict or explain one nearby behavior; correct gently, with evidence.
Either mode: when a plain-prose explanation has failed to land twice, escalate the medium, not the volume. Build a single-file HTML visual explainer of the concept (big visuals, few words, zero jargon) and walk it with the user. One concept per explainer; it teaches, it never argues for an option.
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.
- 7d ago First seen · 53 lines · 86 tokens per session scan A 282514d0ed2a
maestro-coach is a skill published in the GitHub repository ReinaMacCredy/maestro (232 stars, last pushed 6d ago), licensed MIT. It adds 86 tokens to every session and 604 once invoked, about $0.0004 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-05.
Other skills, from other repositories
pn-ai-fluency-curriculum
Design an AI fluency curriculum for a team or organization — skill-level assessment, learning path design, hands-on exercise plans, and progress tracking. Use when onboarding a team to AI agent tooling, building internal AI education programs, or helping individuals move from passive AI use to confident, autonomous AI…
cyrene-diagram
A design guide for making static SVG learning cards: small diagrams or reference cards rendered as images. It explains when to use a card instead of Mermaid, a text-based diagram format, and sets layout, color, size, and safety rules.
onboard
Quick protocol recommendation from recent sessions, or quest-based learning through scenario, trial, and quiz.
frontmcp-guides
Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Use when you want a getting-started guide, a full worked example, or to learn best practices by following a step-by-step build rather than a single API reference. Includes a beginner weather-API server (tool plus static resource, Zod…
create-skill
Create instruction-only skills that package knowledge and workflow guides for AI clients.
learn
Extract reusable patterns from non-trivial work in the is-kit repository and store them as project knowledge. Use after meaningful API design, type-system work, debugging, or compatibility discoveries.