A command for updating the Maestro plugin from its marketplace source and applying the new code to the current session. It also reports recent commits when the plugin is installed as a Git checkout.

Use it to pull the latest marketplace code, inspect recent changes, and reload the session so the update becomes active.

It avoids running newly downloaded plugin code in a session that still has the old version loaded. It also gives a clear error if the update command fails or is unavailable.

update — Command by mbanderas

Install

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.

agentmods

npx agentmods add commands/mbanderas/maestro/update

Clone the repo

git clone --depth 1 https://github.com/mbanderas/maestro

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 587 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00017	$0.00587
Opus 5	$0.00009	$0.00293
Sonnet 5	$0.00003	$0.00117
Haiku 4.5	$0.00002	$0.00059

Measured 2d ago against content hash 20e9bcd65db3, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

update 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.

commands/update.md · 63 lines

What it actually says

Pull the latest Maestro plugin code from the marketplace and guide the user through applying it to the running session.

Maestro pins no plugin version — the marketplace clone always tracks the newest committed code, so a marketplace update followed by a session reload resolves the latest without any manual version bump.

Steps

Pull the latest plugin code via Bash:
```
claude plugin marketplace update maestro
```
This is the non-interactive CLI form of the marketplace update. Capture stdout/stderr. If the command exits non-zero, report the error verbatim and stop. If claude is not on PATH, tell the user to run this command in their terminal manually and skip to step 3.
Report what changed — after a successful update, show the latest commits:
```
git -C "${CLAUDE_PLUGIN_ROOT}" log --oneline -5 2>/dev/null || true
```
If the plugin root is not a git checkout (e.g. a marketplace zip install), note the version is whatever the marketplace published and skip this step.
Reload the running session — the plugin binary is pinned at session start, so the new code is NOT live yet. Tell the user:

Run /reload-plugins in this session to apply the update without restarting. If that command warns or is unavailable, restart Claude Code — the updated plugin loads automatically on next launch.

Do not attempt to run /reload-plugins via Bash; it is an in-session slash command that must be entered by the user in the Claude Code UI.
Post-restart re-sync — on restart the SessionStart hook fires and re-syncs any wired copies (e.g. the statusline context-bar script). This happens automatically; no manual step is needed.
Confirm — report: update pulled, session reload required via /reload-plugins or restart.

Notes:

/reload-plugins applies the new code in-session; a full restart is always a safe fallback.
Do NOT tell the user to run /plugin update maestro — that command does not exist in Claude Code.
If step 2 errors (zip install with no .git, exit 128), do NOT go hunting through the plugin cache with ls/cat/grep/find — just skip it and report the marketplace-published version. Step 1 succeeding is the update.
Do not edit any files.

Changes

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 · 63 lines · 17 tokens per session scan A 20e9bcd65db3

Subscribe to this mod's changes

update is a command published in the GitHub repository mbanderas/maestro (5 stars, last pushed 5d ago), licensed MIT. It adds 17 tokens to every session and 587 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.

Data and AI E-commerce Git and workflow LLM ai-agents claude-code codex cursor developer-tools

update

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Steps

What this file has done since we first saw it

Other commands, from other repositories

fastapi_stripe

start-feature

tray-validar-integracao

git-sync-workspace

migrate-rest-to-graphql

optimize-listing