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/tinhtran24/maestro/projectgit clone --depth 1 https://github.com/tinhtran24/maestroWrote 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.
[](https://agentmods.dev/commands/tinhtran24/maestro/project)<a href="https://agentmods.dev/commands/tinhtran24/maestro/project"><img src="https://agentmods.dev/badge/commands/tinhtran24/maestro/project.svg" alt="Measured on agentmods" height="20"></a>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.00000 | $0.01086 |
| Opus 5 | $0.00000 | $0.00543 |
| Sonnet 5 | $0.00000 | $0.00217 |
| Haiku 4.5 | $0.00000 | $0.00109 |
Grade A, and why
project 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 3d 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 — 164 lines — stays where its author put it; the contents beside it link to each section on GitHub.
to project
Manage projects: register repos, inspect, configure per-project settings, and remove.
Syntax
maestro project <subcommand> [args] [flags]
Subcommands
to project add
Register a local git repo as a project so sessions can be spawned in it. The path must be an existing git repository on disk. With --as-workspace, the path may be a parent folder containing direct child git repositories; Maestro initializes/adopts the parent as the root repo and gitignores children.
Syntax:
maestro project add [flags]
Flags:
| Flag | Meaning | Default / Required |
|---|---|---|
--as-workspace |
Register a parent folder as a workspace project (root-as-repo plus direct child repos) | - |
--id string |
Project id | Derived by the daemon from the path |
--name string |
Display name | - |
--orchestrator-agent string |
Default orchestrator session agent | - |
--path string |
Absolute path to the local git repo | Required |
--worker-agent string |
Default worker session agent | - |
Examples:
# Register a repo as a project
maestro project add --path /Users/harshit/Downloads/side-quests/maestro --name "maestro"
# Register a workspace (parent folder containing multiple repos)
maestro project add --path /Users/harshit/Downloads/side-quests --as-workspace --name "side-quests"
to project ls
List registered projects. Aliases: ls, list.
Syntax:
maestro project ls [flags]
Flags:
| Flag | Meaning | Default / Required |
|---|---|---|
--json |
Output projects as JSON | - |
Examples:
# List all registered projects
maestro project ls
to project get
Fetch one registered project.
Syntax:
maestro project get <id> [flags]
Flags:
| Flag | Meaning | Default / Required |
|---|---|---|
--json |
Output project as JSON | - |
Examples:
# Get details for the maestro project
maestro project get maestro
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.
- 3d ago First seen · 164 lines · 0 tokens per session scan A 11492a7052cb
project is a command published in the GitHub repository tinhtran24/maestro (3 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 1,086 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
agent-router
전문 에이전트 자동 라우팅. 법률, 재무, 특허, SEO, 마케팅, 기획, BM 설계(BMC/Lean/JTBD/Wardley/Blue Ocean/Lightning Sprint), 코드리뷰, 아키텍처, 견적, CRM, HR/인사, 노무(노동법/해고/산재/취업규칙), 리서치, 데이터 분석, 제1원칙 사고, 주식 투자, 부동산 투자, 명리학, 회사운영(노란우산/창업혜택/고용지원/세무일정), 디자인 제작(배너/카드뉴스/SNS/광고/인포그래픽), FAQ/지식베이스(KCS/셀프서비스/아티클), 고객지원(CS응답/에스컬레이션) 등 50+ 에이전트.
loops
Weekly review — surface everything in-flight and force a ship / block / kill decision on each.
contribute-to
Join an EXISTING, in-progress work item (issue or PR) as a contributor — walk the contribution loop toward a human-stated goal and success criteria, without the full spec chain.
ask
Ask a human a question on the work item — the way a spawned agent escalates.
channels
Operate the communication channels — the back-and-forth surfaces beside the work item, starting with the Slack bot (issue-245).
work-on
Run "the-loop" on a work item (GitHub issue or Jira id) end-to-end — requirements → design → testing plan → tasks → execute → verify, with self/critic review.