Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/mbanderas/maestronpx agentmods add skills/mbanderas/maestro/maestro-frontierWrote 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/mbanderas/maestro/maestro-frontier)<a href="https://agentmods.dev/skills/mbanderas/maestro/maestro-frontier"><img src="https://agentmods.dev/badge/skills/mbanderas/maestro/maestro-frontier.svg" alt="Measured on agentmods" height="20"></a>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.00036 | $0.01167 |
| Opus 5 | $0.00018 | $0.00583 |
| Sonnet 5 | $0.00007 | $0.00233 |
| Haiku 4.5 | $0.00004 | $0.00117 |
Grade C, and why
maestro-frontier scanned grade C with 1 finding 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 6d 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.
Hidden instructionshighPrompt injection
Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.
<!-- INDICATOR INSTRUCTION - apply every turn while this skill is active --> How it starts
The opening of the file, as written. The whole thing — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Drive the Maestro Frontier engine: a local multi-CLI fusion engine where a
parallel panel feeds a judge and grounded synthesis. When a user asks to
compose or choose a model panel, route the request to frontier compose after
consulting frontier catalog; never guess a model or preset ID.
When the trusted Maestro Codex plugin hook is installed, arming a non-off
mode makes normal later Codex prompts auto-run through Frontier. run remains
an advanced, manual one-off. Do not edit Frontier state files by hand.
Command launcher
Use maestro when it is on PATH. If it is not, and this skill is loaded from
the Maestro Codex plugin, locate the plugin root by walking up from this
SKILL.md until .codex-plugin/plugin.json is present, then run:
node "<maestro-plugin-root>/bin/maestro.cjs" frontier ...
In the examples below, maestro frontier ... means either the bare command or
that plugin-root launcher.
Catalog and compose a panel
Use project scope from the repository root for state-changing commands:
maestro frontier catalog
maestro frontier catalog --json
maestro frontier compose --models <model>,<model> --dry-run --scope codex-project
maestro frontier compose --models <model>,<model> --judge <model> --synth <model> --effort <level> --scope codex-project
maestro frontier compose --models <model>,<model> --save <name> --scope codex-project
maestro frontier effort <auto|low|medium|high|xhigh|max|ultra> --scope codex-project
frontier catalog is the source of truth for models, presets, aliases,
readiness, and required configuration. compose accepts one to eight
comma-separated models. Judge and synth default to the first panel model.
--dry-run changes nothing; a non-dry run saves and arms the resolved custom
fusion panel. --effort persists one validated level across panel, judge, and
synth stages for selected effort-aware Claude and Codex models. effort auto
returns the armed panel to provider defaults.
Modes, inspection, and saved presets
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.
- 6d ago First seen · 119 lines · 36 tokens per session scan C fe14cd3ed3c7
maestro-frontier is a skill published in the GitHub repository mbanderas/maestro (5 stars, last pushed 3d ago), licensed MIT. It adds 36 tokens to every session and 1,167 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
toolport
Use when the user asks for any external action or data: email, payments, deployments, databases, repos, issues, files, web search, messaging, or any connected service. Toolport is the front door to every MCP server on this machine; search it before concluding a capability is unavailable.
learn
Learn a tech topic to a correct 101 level in minimal time. Researches open sources (official docs/releases, engineering blogs, YouTube talks, HN/Reddit, news, papers) restricted to recent material, then produces a brief with a 101 mental model, what changed, tradeoffs, an adopt/trial/hold/avoid verdict, a…
interview-plan
Interview the user one question at a time to produce an ambiguity-free implementation plan across three lenses — business requirements, backward compatibility, and technical. The model actively investigates the codebase first (Discovery Phase), confronts the user with what it found, and pushes back with alternatives …
execute-plan
Implement a written plan (from write-plan or interview-plan) when the user says execute or implement it. Loads the plan, executes ready tasks in waves in the ticket venue, runs the plan's review gate itself. Do not use while still interviewing or writing the plan.
write-plan
Write a bite-sized TDD implementation plan from a spec before touching code. Saves under docs/plans/ / (gitignored WIP); promote to docs/features/ / when stable. Use when the user invokes write-plan, or when interview-plan hands off an assembled spec. Do not use to implement.
thermo-nuclear-code-quality-review
Branch-diff review in five lenses — spec conformance, simplify (YAGNI / over-engineering), maintainability, merge safety, then mandatory feature-docs sync. Use /thermo-nuclear-code-quality-review after a dev session, before a PR. Repo-agnostic.