maestro: Command for Claude Code

.claude/commands/update-from-template.md

update-from-template is a command for Claude Code from CarlosDanielDev/maestro. It costs 0 tokens per session (413 once invoked), scanned A, original, MIT.

A command that compares the shared Maestro template with a downstream project's .claude configuration and syncs safe updates. It reports new, changed, identical, and locally customized files.

In plain words
What is it for?
Use it to update a project's agent commands and instructions from the template, either in the current directory or at a supplied project path.
Why use it?
It avoids overwriting project-specific edits while showing which template changes can be applied and which need manual merging.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; mentions CLAUDE.md; mentions subagents.

This is CarlosDanielDev/maestro's own configuration. It tells Claude Code how to work on maestro itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything maestro configures →

Reuse

Borrowing it

Nothing to install: this file belongs to CarlosDanielDev/maestro. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/CarlosDanielDev/maestro/main/.claude/commands/update-from-template.md
Clone the repo
git clone --depth 1 https://github.com/CarlosDanielDev/maestro

Made for: Claude Code.

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

agentmods badge for update-from-template

README.md
[![agentmods](https://agentmods.dev/badge/commands/carlosdanieldev/maestro/update-from-template/github.svg)](https://agentmods.dev/commands/carlosdanieldev/maestro/update-from-template)
Your own site
<a href="https://agentmods.dev/commands/carlosdanieldev/maestro/update-from-template"><img src="https://agentmods.dev/badge/commands/carlosdanieldev/maestro/update-from-template/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.

agentmods 80×15 button for update-from-template

Your own site · 80×15
<a href="https://agentmods.dev/commands/carlosdanieldev/maestro/update-from-template"><img src="https://agentmods.dev/badge/commands/carlosdanieldev/maestro/update-from-template.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 413 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00413
Opus 5.5 $0.00000 $0.00165
Sonnet 5.5 $0.00000 $0.00083
Haiku 4.5 $0.00000 $0.00041

Measured 1mo ago against content hash 5bbf57984feb, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

update-from-template 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 1mo 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.

.claude/commands/update-from-template.md · 70 lines

What it actually says

Update From Template

Sync template updates from Maestro into a downstream project's .claude/ directory.

Usage: /update-from-template or /update-from-template /path/to/project


Arguments

$ARGUMENTS optionally contains the path to the target project.

If no path provided, use the current working directory.


Instructions

Step 1: Locate Template

Find the Maestro template at template/.claude/ in the maestro project.

Step 2: Compare Files

For each file in template/.claude/:

  1. Check if it exists in the target project's .claude/
  2. If it exists, compare content
  3. Categorize as: NEW, UPDATED, IDENTICAL, or CUSTOMIZED

CUSTOMIZED = file exists but has user modifications beyond the template. These should NOT be overwritten.

Step 3: Present Diff Report

Template Sync Report
====================

NEW (will be added):
  .claude/commands/new-command.md

UPDATED (template changed, your version is default):
  .claude/agents/subagent-architect.md

IDENTICAL (no changes needed):
  .claude/agents/subagent-docs-analyst.md

CUSTOMIZED (will NOT overwrite — manual merge needed):
  .claude/CLAUDE.md (you customized the tech stack)
  .claude/skills/project-patterns/SKILL.md (your project patterns)

Apply updates? (NEW + UPDATED only) [y/n]

Step 4: Apply Updates

Only apply NEW and UPDATED files. Never overwrite CUSTOMIZED files.

Step 5: Report Completion

Template sync complete.

Applied:
  + .claude/commands/new-command.md (NEW)
  ~ .claude/agents/subagent-architect.md (UPDATED)

Skipped (manual merge needed):
  .claude/CLAUDE.md — compare with template/.claude/CLAUDE.md
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.

  1. 1mo ago First seen · 70 lines · 0 tokens per session scan A 5bbf57984feb

Subscribe to this mod's changes

update-from-template is a command published in the GitHub repository CarlosDanielDev/maestro (31 stars, last pushed 20d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 413 tokens. 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-10-02.

Related

update-from-template compared with commands from other repositories

update-from-template next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
update-from-templateCarlosDanielDev/maestroCommand3120d agoMITA0Claude Code
merge-conflict-analysisrjmurillo/ai-agentsCommand49yesterdayMITA0GitHub Copilot
release-notesOpenHands/extensionsCommand176yesterdayMITA44Claude Code
commitechoVic/blade-codeCommand18124d agoMITA8Claude Code
repo-audittractorjuice/arc-kitCommand2.3k2d agononeA29Claude Code
propsmill/infrahub-mcpCommand10yesterdayApache-2.0A18Claude Code
codex-reviewoalders/kitchen-sinkCommand53d agoMITA41Claude Code