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 skills add catlog22/maestro-flow --skill maestro-companiongit clone --depth 1 https://github.com/catlog22/maestro-flowWrote 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/skills/catlog22/maestro-flow/maestro-companion)<a href="https://agentmods.dev/skills/catlog22/maestro-flow/maestro-companion"><img src="https://agentmods.dev/badge/skills/catlog22/maestro-flow/maestro-companion/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/skills/catlog22/maestro-flow/maestro-companion"><img src="https://agentmods.dev/badge/skills/catlog22/maestro-flow/maestro-companion.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.00034 | $0.01729 |
| Opus 5.5 | $0.00014 | $0.00692 |
| Sonnet 5.5 | $0.00007 | $0.00346 |
| Haiku 4.5 | $0.00003 | $0.00173 |
Grade A, and why
maestro-companion 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 yesterday.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- yesterday Changed 1b3ec3c2cd03
- 8d ago Changed 873bf45bfc0c
- 9d ago Changed · +1 lines ae3925f44809
- 22d ago Changed c082d943512c
- 25d ago Changed 1924a7d76cdd
- 28d ago Changed a316bb29cc56
- 1mo ago Changed a3b763625b70
- 1mo ago Changed 5fa937b7bf8a
- 1mo ago First seen · 171 lines · 34 tokens per session scan A 75919042a29d
maestro-companion is a skill published in the GitHub repository catlog22/maestro-flow (566 stars, last pushed yesterday), with no licence file. It adds 34 tokens to every session and 1,729 once invoked, about $0.0001 per session on Opus 5.5. 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-09-03.
Other skills, from other repositories
day-log
Quick timestamped log entry — no conversation, just capture.
period-summary
Period summary (w/m/q/y) — reflect on the period, score it, close it out.
delegate
Orchestrate multiple CLI agents in parallel — delegate tasks to claude/gemini/codex/opencode/rust-code via .tasks/ system. Use when "delegate to", "spawn agents", "parallel analysis", "send task to claude", "run in background", "orchestrate agents". Do NOT use for in-process sub-agents (use spawnagent) or single bash…
day-start
Day briefing — deliver context, capture what's happened, get moving.
bighead
Autonomous task loop — iterate on a task until done, commit after each step, run tests. Use when "run in loop", "autonomous mode", "keep working", "don't stop", "bighead mode", "--loop". Do NOT use for one-shot tasks (just run normally) or self-improvement (use /self-evolve).
day-summary
Evening summary — reflect on the day, score it, close it out.