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-knowhowgit 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-knowhow)<a href="https://agentmods.dev/skills/catlog22/maestro-flow/maestro-knowhow"><img src="https://agentmods.dev/badge/skills/catlog22/maestro-flow/maestro-knowhow/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-knowhow"><img src="https://agentmods.dev/badge/skills/catlog22/maestro-flow/maestro-knowhow.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.00683 |
| Opus 5.5 | $0.00051 | $0.00273 |
| Sonnet 5.5 | $0.00026 | $0.00137 |
| Haiku 4.5 | $0.00013 | $0.00068 |
Grade A, and why
maestro-knowhow 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 6ab6772e1cf2
- 12d ago Changed c3662a2cda87
- 19d ago Changed f726cd14036e
- 20d ago Changed 29c85d1f53d6
- 1mo ago Changed d8dafa9a5fde
- 1mo ago Changed dfbdaa77c2b8
- 1mo ago Changed 95af6f904038
- 1mo ago Changed 9daf32c627fa
- 1mo ago Changed c9bd1d9f7c38
- 1mo ago First seen · 45 lines · 128 tokens per session scan A 85d2f1060565
maestro-knowhow is a skill published in the GitHub repository catlog22/maestro-flow (569 stars, last pushed yesterday), with no licence file. It adds 128 tokens to every session and 683 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
memory
Expertise in maintaining persistent bot memory, synchronizing with previous sessions via the Task Ledger, and preserving decision logs.
brainctl
Unified agent memory CLI — read, write, search, and maintain the shared memory spine (brain.db). Use for persistent cross-session memory, knowledge graph, event logging, decisions, affect tracking, and consolidation.
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.
graft
Persistent graph memory shared across conversations and agents. Graft is a prompter, not a cache: it hands you notes that may be close to the problem in front of you, and a close note is already a win - it gives you a starting point and reminds you what was decided before. Search it before non-trivial work, and write…
memory-audit
Maintenance pass + health check of the graft graph. Runs the graft maintain loop: checks what is due, applies the mechanical cleanup, then adjudicates every maintenance candidate (near duplicates, supersessions, contradictions, memories whose source file changed or disappeared, keyword variants, stale low-value notes)…
memoryze
Distill the current conversation (or a specified excerpt) into N high-quality graft nodes and save them. Triggered by /memoryze, "save this to memory", "ricorda questo", "memorize this", or whenever the user explicitly wants the agent to commit knowledge to the persistent graph. The user can hint at granularity…