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 agentmods add commands/mbanderas/maestro/settingsgit clone --depth 1 https://github.com/mbanderas/maestroWhat 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 | $0.00027 | $0.01609 |
| Opus 5 | $0.00014 | $0.00805 |
| Sonnet 5 | $0.00005 | $0.00322 |
| Haiku 4.5 | $0.00003 | $0.00161 |
Grade A, and why
settings 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 2d 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
See and change Maestro's toggles: terse output, the frontier fusion engine,
the context-bar status line, the discipline enforcement-hook pack, and the
verify-gate Stop hook (warn/block/off). compress is an action, not a
toggle, so it is not shown here.
Two ways to use it. With no arguments it opens a keyboard picker. With arguments it runs the change directly and finishes — no questionnaire.
One writer owns all state: settings/cli.cjs, which reads and writes the
existing stores. This command never edits those files directly; it
always goes through the CLI so the existing readers stay in sync. Throughout,
SCLI = node "${CLAUDE_PLUGIN_ROOT}/settings/cli.cjs".
Requested action: $ARGUMENTS
Route on $ARGUMENTS
Trim it and split into tokens. The first token selects the path; anything non-empty skips the picker entirely.
- empty → run the Interactive picker section below.
status(optionally--json) → runSCLI status [--json], print it, stop.list(optionally--json) → runSCLI list [--json], print it, stop.help,-h,--help, or anything unrecognized → runSCLI help, print it (usage grammar + the full value matrix), stop. For an unrecognized token, say so first, then show help.set <key> <value> [flags]→ pass straight through:SCLI set <key> <value> [--judge M] [--synth M] [--models a,b,c].- shorthand — first token is a key (
terse,frontier,context-bar,bar,discipline, orverify): treat the rest as the value and runSCLI set <key> <value>.
Normalizing the value (both set and shorthand)
The CLI takes one frontier value with a colon (single:opus,
fusion:opus-gpt). Accept the friendlier space form and normalize:
frontier off→SCLI set frontier offfrontier single opus→SCLI set frontier single:opusfrontier fusion opus-gpt→SCLI set frontier fusion:opus-gptfrontier fusion custom --models opus,gpt-5.5,gemini→SCLI set frontier fusion:custom --models opus,gpt-5.5,geminifrontier fusion opus-gpt --judge opus --synth gpt-5.5→ pass the flags through- already-coloned (
frontier fusion:opus-gpt) → pass as-is terse ultra,context-bar off,discipline off,verify block→SCLI set terse ultra,SCLI set context-bar off,SCLI set discipline off,SCLI set verify block
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.
- 2d ago First seen · 115 lines · 27 tokens per session scan A c34083ea3cd4
settings is a command published in the GitHub repository mbanderas/maestro (5 stars, last pushed 5d ago), licensed MIT. It adds 27 tokens to every session and 1,609 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 commands, from other repositories
upgrade
Upgrade the skillshare CLI binary and/or the built-in skillshare skill.
everme-help
Print a concise EverMe plugin status + reference card.
release
Walk the llmwiki release process step by step.
add-agent
引导新增一个 Agent 适配器。用法 /add-agent.
migrate
Command "migrate" from chohra-med/expo_boilerplate, covering invocation, steps and rule.
cost-tracker
Track session costs, understand token spend, and get optimization tips.