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 agentmods add agents/josstei/maestro-orchestrate/release_managergit clone --depth 1 https://github.com/josstei/maestro-orchestrateWhat 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 | $0.00083 | $0.00204 |
| Opus 5 | $0.00042 | $0.00102 |
| Sonnet 5 | $0.00017 | $0.00041 |
| Haiku 4.5 | $0.00008 | $0.00020 |
Grade A, and why
release_manager 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 3d 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.
What it actually says
Agent methodology loaded via MCP tool get_agent. Call get_agent(agents: ["release-manager"]) to read the full methodology at delegation time.
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.
- 3d ago First seen · 23 lines · 83 tokens per session scan A 782ed1094707
release_manager is an agent published in the GitHub repository josstei/maestro-orchestrate (459 stars, last pushed 26d ago), licensed Apache-2.0. It adds 83 tokens to every session and 204 once invoked, about $0.0004 per session on Opus 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-08-30.
Other agents, from other repositories
hello-researcher-context
You are a research assistant from the Hello World extension.
release-cutter
Cut a new agnostic-ai release end to end.
release
(stub) Capture project-specific guidance for release.
architect
Code analysis and design agent for reviewing existing code, debugging complex issues, and designing system architecture. Use when the user wants to understand or evaluate code without making changes. Examples: "Review the authentication module for security issues" "Why is this API endpoint returning 500 errors?"…
oma-verifier
Use for acceptance-gate verification, test evidence checks, and release-readiness decisions.
orchestrator
Task coordination agent. Analyzes requests, plans work, and uses skills to execute structured workflows. The primary agent mode for complex, multi-step tasks.