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.
git clone --depth 1 https://github.com/josstei/maestro-orchestrateWrote 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/agents/josstei/maestro-orchestrate/tester)<a href="https://agentmods.dev/agents/josstei/maestro-orchestrate/tester"><img src="https://agentmods.dev/badge/agents/josstei/maestro-orchestrate/tester/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/agents/josstei/maestro-orchestrate/tester"><img src="https://agentmods.dev/badge/agents/josstei/maestro-orchestrate/tester.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.00066 | $0.00176 |
| Opus 5.5 | $0.00026 | $0.00070 |
| Sonnet 5.5 | $0.00013 | $0.00035 |
| Haiku 4.5 | $0.00007 | $0.00018 |
Grade A, and why
tester 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 today.
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: ["tester"]) 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.
- today Changed · -2 lines f0a31f474b42
- 1mo ago First seen · 24 lines · 66 tokens per session scan A 8564a983e256
tester is an agent published in the GitHub repository josstei/maestro-orchestrate (485 stars, last pushed today), licensed Apache-2.0. It adds 66 tokens to every session and 176 once invoked, about $0.0003 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-08-30.
Other agents, from other repositories
plan-reviewer
Review docs/PLAN.md and docs/tasks/.md for RTM coverage, Stub-First compliance, and task atomicity. Spawn after planner to gate the Planning→Execution boundary.
code-reviewer
Review implemented code for Compliance with task requirements, Quality (logic, edge cases), Testing (E2E pass, no over-mocking), and Docs (.AGENTS.md, docstrings updated). Spawn after developer to gate Execution→Merge.
test-writer
Writes and maintains the node:test suite and fixtures for this repo.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
test-writer
Use this agent to identify and test a distinct, realistic regression that existing tests do not catch, including during test-driven development. Do not generate a comprehensive suite by default. Invoke /writing-tests before changing test setup or assertions.\n\nExamples:\n \nContext: The user has just implemented a…
sdd-verify
Verify implementation against SDD specs, tasks, strict TDD evidence, and review workload boundaries.