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-forkgit 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-fork)<a href="https://agentmods.dev/skills/catlog22/maestro-flow/maestro-fork"><img src="https://agentmods.dev/badge/skills/catlog22/maestro-flow/maestro-fork/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-fork"><img src="https://agentmods.dev/badge/skills/catlog22/maestro-flow/maestro-fork.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.00014 | $0.01328 |
| Opus 5.5 | $0.00006 | $0.00531 |
| Sonnet 5.5 | $0.00003 | $0.00266 |
| Haiku 4.5 | $0.00001 | $0.00133 |
Grade A, and why
maestro-fork 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 a34d911527ea
- 8d ago Changed 5ef6f78af8dc
- 9d ago Changed c013277fdcb0
- 22d ago Changed 6d088e89f5e4
- 25d ago Changed 9d8121fffbff
- 28d ago Changed 035727823936
- 1mo ago Changed 96b3138d3d1a
- 1mo ago Changed c35ba892ef77
- 1mo ago First seen · 131 lines · 14 tokens per session scan A e691a2124281
maestro-fork is a skill published in the GitHub repository catlog22/maestro-flow (566 stars, last pushed yesterday), with no licence file. It adds 14 tokens to every session and 1,328 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
prs
Expertise in managing the Git and GitHub Pull Request lifecycle, including staging changes, generating PR descriptions, and branch management.
ccmanager-config
Set up, review, or repair a CCManager config — .ccmanager.json at a git repository root, or the global /.config/ccmanager/config.json. Use when someone wants ccmanager to launch a different agent CLI (codex, gemini, cursor-agent, copilot…), add command presets, run a command on session state changes or worktree…
ccb-github
Maintain this CCB project's GitHub-facing release and npm publication surface. Use when preparing, publishing, auditing, or fixing CCB releases; updating README.md, README/zh.md, localized README files, CHANGELOG.md, VERSION, package.json, GitHub release notes/assets, repository description/topics, npm registry state…
cli-collaboration
Use when multiple CLI agents or assistants alternate on the same repository or explicit shared handoff workflow — especially with AGENTHANDOFF.md, side-by-side AGENTS.md/CLAUDE.md/GEMINI.md, dirty worktrees, ownership notes, red tests, resume/continue requests, or /cli-collaboration in Grok Build.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.