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.
git 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/session)<a href="https://agentmods.dev/commands/tinhtran24/maestro/session"><img src="https://agentmods.dev/badge/commands/tinhtran24/maestro/session/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.
<a href="https://agentmods.dev/commands/tinhtran24/maestro/session"><img src="https://agentmods.dev/badge/commands/tinhtran24/maestro/session.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00000 | $0.00936 |
| Opus 5.5 | $0.00000 | $0.00374 |
| Sonnet 5.5 | $0.00000 | $0.00187 |
| Haiku 4.5 | $0.00000 | $0.00094 |
Grade A, and why
session 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.
How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
to session
Manage agent sessions: list, inspect, rename, kill, restore, clean up, and claim PRs.
Syntax
maestro session <subcommand> [args] [flags]
Subcommands
to session ls
List sessions.
Syntax:
maestro session ls [flags]
Flags:
| Flag | Meaning | Default / Required |
|---|---|---|
-a, --all |
Include orchestrator sessions | - |
--include-terminated |
Include terminated sessions | - |
--json |
Output as JSON | - |
-p, --project string |
Filter by project ID | - |
Examples:
# List all active worker sessions
maestro session ls
# List all sessions including terminated, scoped to one project
maestro session ls --include-terminated -p maestro
to session get
Fetch one session.
Syntax:
maestro session get <id> [flags]
Flags:
| Flag | Meaning | Default / Required |
|---|---|---|
--json |
Output as JSON | - |
-p, --project string |
Project id to scope the lookup | - |
Examples:
# Get details for session mer-3
maestro session get mer-3
# Get session details as JSON
maestro session get mer-3 --json
to session kill
Terminate a session.
Syntax:
maestro session kill <id> [flags]
Flags:
| Flag | Meaning | Default / Required |
|---|---|---|
-p, --project string |
Project id to scope the lookup | - |
Examples:
# Kill session mer-3
maestro session kill mer-3
to session rename
Rename a session.
Syntax:
maestro session rename <id> <name> [flags]
Flags:
| Flag | Meaning | Default / Required |
|---|---|---|
-p, --project string |
Project id to scope the lookup | - |
Examples:
# Rename session mer-3 to a new display name
maestro session rename mer-3 "fix-auth-bug"
to session restore
Relaunch a terminated session.
Syntax:
maestro session restore <id> [flags]
Flags:
| Flag | Meaning | Default / Required |
|---|---|---|
-p, --project string |
Project id to scope the lookup | - |
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.
- 1mo ago First seen · 207 lines · 0 tokens per session scan A da1a74ff6366
session is a command published in the GitHub repository tinhtran24/maestro (6 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 936 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
version
Display current guide and Claude Code versions.
diff-docs
Compare official Anthropic docs baseline vs current snapshot (no network — instant).
security-review
A security review procedure based on CWE, a list of common software weaknesses, and STRIDE, a method for identifying threats to a system.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.
docs-review
Phase 4 of documenting-projects: Quality gate with 8 measurable criteria and iteration. Triggers: '/docs-review', invoked by documenting-projects orchestrator.
triage-github
Scan GitHub repos for activity, generate a summary, and create actionable GTD tasks.