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/attachgit 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.01827 |
| Opus 5 | $0.00000 | $0.00914 |
| Sonnet 5 | $0.00000 | $0.00365 |
| Haiku 4.5 | $0.00000 | $0.00183 |
Grade A, and why
attach 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 — 337 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔸 attach
Command to create orchestra members (Git worktrees) from existing branches. Allows you to attach to local or remote branches to create independent development environments.
Overview
mst attach [branch-name] [options]
mst a [branch-name] [options] # alias
Usage Examples
Basic Usage
# Interactive branch selection from available branches
mst attach
# Attach to specific local branch
mst attach feature/existing-feature
# Include remote branches in selection
mst attach --remote
# Attach to specific remote branch
mst attach origin/feature/remote-branch --remote
Advanced Usage
# Fetch latest remote data before listing branches
mst attach --fetch --remote
# Attach and open in editor with environment setup
mst attach feature/api --open --setup
# Attach and execute command
mst attach bugfix/issue-123 --exec "npm test"
# Attach and enter shell session
mst attach feature/new --shell
Options
| Option | Short | Description | Default |
|---|---|---|---|
--remote |
-r |
Include remote branches in selection | false |
--fetch |
-f |
Fetch from remote before listing branches | false |
--open |
-o |
Open in editor (Cursor/VSCode) after attachment | false |
--setup |
-s |
Run environment setup (npm install) | false |
--shell |
Enter shell session after attachment | false |
|
--exec <command> |
Execute command after attachment | none |
Branch Selection
Interactive Mode
When no branch name is provided, displays an interactive menu:
? Which branch would you like to attach to?
❯ [local] feature/authentication
[local] bugfix/login-issue
[remote] origin/feature/api-v2
[remote] origin/hotfix/security-patch
Available Branches
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 · 337 lines · 0 tokens per session scan A 7a646ae1f0a7
attach 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 1,827 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.
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.
audit-quiz-coverage
Find quiz coverage gaps from recent guide/CHANGELOG/CC-releases changes and propose new questions.
worktree
Create a git worktree for isolated feature/fix work.
sync
Check guide/landing synchronization status.
version
Display current guide and Claude Code versions.