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-terseWrote 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-terse)<a href="https://agentmods.dev/skills/mbanderas/maestro/maestro-terse"><img src="https://agentmods.dev/badge/skills/mbanderas/maestro/maestro-terse.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.00023 | $0.00461 |
| Opus 5 | $0.00012 | $0.00230 |
| Sonnet 5 | $0.00005 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
maestro-terse 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.
What it actually says
Toggle the Maestro terse output level for this environment. Terse mode
condenses agent narration, not requested artifacts; levels range from off
(default verbosity) through lite, full, and ultra (most compressed).
When the user invokes this skill, run the settings CLI to read or change the terse level. Do not edit settings files by hand.
Command launcher
Use node settings/cli.cjs when Maestro is installed in the project root. If
that file is not present 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>/settings/cli.cjs" ...
Check current terse level
node settings/cli.cjs --help
Consult the help output for the exact read subcommand, then run it. If
settings/cli.cjs is not present, use the plugin-root launcher above.
Set terse level
node settings/cli.cjs set terse <level>
Valid levels: off | lite | full | ultra
Examples:
node settings/cli.cjs set terse off
node settings/cli.cjs set terse lite
node settings/cli.cjs set terse full
node settings/cli.cjs set terse ultra
If the CLI rejects an argument or the subcommand name differs, run
node settings/cli.cjs --help first and follow the printed usage.
Notes
- The change persists in Maestro's settings store; it applies to subsequent agent turns in this project.
- Preserve the requested voice, genre, rhetoric, formatting, and necessary length of artifacts unless the user explicitly asks for terse artifact copy.
- Requires
nodeonPATH. A project-local Maestro install is optional when the skill is loaded from the Maestro Codex plugin.
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 First seen · 62 lines · 23 tokens per session scan A 6ff86c93807a
maestro-terse is a skill published in the GitHub repository mbanderas/maestro (5 stars, last pushed 5d ago), licensed MIT. It adds 23 tokens to every session and 461 once invoked, about $0.0001 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-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.
brainstorm
Use when the user explicitly asks for brainstorming, pre-ticket discovery, fuzzy product shaping, visual option exploration, or turning an idea into an approved design before implementation planning.