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/mirinodev/maestro/listgit clone --depth 1 https://github.com/mirinodev/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.00000 | $0.02709 |
| Opus 5 | $0.00000 | $0.01354 |
| Sonnet 5 | $0.00000 | $0.00542 |
| Haiku 4.5 | $0.00000 | $0.00271 |
Grade A, and why
list 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 — 351 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔸 list
Command to display a list of created orchestra members (Git worktrees). You can check the status, metadata, and GitHub integration status of each orchestra member.
Overview
mst list [options]
mst ls [options] # alias
Usage Examples
Basic Usage
# Display list of orchestra members
mst list
# Output in JSON format
mst list --json
# Display with metadata
mst list --metadata
# Select with fzf (outputs selected branch name)
mst list --fzf
# Display full paths
mst list --full-path
Options
| Option | Short | Description | Default |
|---|---|---|---|
--json |
-j |
Output in JSON format | false |
--metadata |
-m |
Display with metadata | false |
--fzf |
-f |
Select mode with fzf | false |
--filter |
Filter by branch name or path | "" |
|
--sort |
Sort by field (branch, age, size) | branch |
|
--last-commit |
Show last commit information | false |
|
--full-path |
Show full paths instead of relative | false |
|
--names |
Machine-readable output (for scripting) | false |
Output Formats
Normal Output
Path display format depends on the ui.pathDisplay configuration setting in .maestro.json:
With "pathDisplay": "absolute" (default):
🎼 Orchestra Members (worktree):
📍 refs/heads/main /Users/user/project
🎷 feature/auth /Users/user/project/.git/orchestrations/feature-auth
🎷 bugfix/login /Users/user/project/.git/orchestrations/bugfix-login
🎷 issue-123 /Users/user/project/.git/orchestrations/issue-123
With "pathDisplay": "relative":
🎼 Orchestra Members (worktree):
📍 refs/heads/main .
🎷 feature/auth .git/orchestrations/feature-auth
🎼 bugfix/login .git/orchestrations/bugfix-login
🎷 issue-123 .git/orchestrations/issue-123
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 · 351 lines · 0 tokens per session scan A 902672ab33a2
list is a command published in the GitHub repository mirinodev/maestro (9 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,709 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-08-31.
Other commands, from other repositories
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
audit-repo-docs
Audit repository documentation against 85+ best practices from claude-code-ultimate-guide.
security-audit
Comprehensive security audit of your project AND Claude Code configuration. Analyzes secrets exposure, injection surfaces, dependencies, hook security, and produces a scored security posture assessment.
retex
Retex - Capture lesson learned dans memory après fix, rollback, erreur.
track-mentions
Search for new online mentions of the Claude Code Ultimate Guide and update the tracker.
version
Display current guide and Claude Code versions.