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-issuegit 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-issue)<a href="https://agentmods.dev/skills/catlog22/maestro-flow/maestro-issue"><img src="https://agentmods.dev/badge/skills/catlog22/maestro-flow/maestro-issue/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-issue"><img src="https://agentmods.dev/badge/skills/catlog22/maestro-flow/maestro-issue.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.00128 | $0.00503 |
| Opus 5.5 | $0.00051 | $0.00201 |
| Sonnet 5.5 | $0.00026 | $0.00101 |
| Haiku 4.5 | $0.00013 | $0.00050 |
Grade A, and why
maestro-issue 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 bfc5c1b96eda
- 8d ago Changed 81b485cc4fc4
- 9d ago Changed 67fe84f93695
- 22d ago Changed 682b4b3cae4b
- 25d ago Changed a6416117be97
- 28d ago Changed b67844c2c37f
- 1mo ago Changed 2f8114dcb2fc
- 1mo ago Changed cede2589e792
- 1mo ago First seen · 49 lines · 128 tokens per session scan A 963d17f154eb
maestro-issue is a skill published in the GitHub repository catlog22/maestro-flow (566 stars, last pushed yesterday), with no licence file. It adds 128 tokens to every session and 503 once invoked, about $0.0005 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
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
sibyl
Persistent memory and task coordination for this project. Invoke for any prompt about past work, project state, in-progress tasks, prior decisions, gotchas, or capturing a non-obvious learning. Also covers semantic search across project knowledge and external docs.
plan-tree
Maintain a structured planning document tree made of roadmap/status files, implementation status or handoff TODO files, topic notes, decision records, open questions, ideas/inspiration pools, and repository/file-structure hygiene plans. Use when Codex needs to create, reorganize, audit, or update a multi-file plan…
capture-task
Capture a new task — create a draft or pending Task record from a rough idea or detailed spec. Use when asked to "add a task", "log a bug", "create a task", or "add to backlog".
refine-backlog
Refine the backlog — screen drafts, remove duplicates, fill in missing details, classify, link, and move to pending.
implement-task
Pick up and work on a binder Task — investigate bugs, discuss open questions, design solutions, write tests, or implement code. Use when asked to "work on", "pick up", "implement", or "fix" a task.