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/performance-engineer)<a href="https://agentmods.dev/agents/josstei/maestro-orchestrate/performance-engineer"><img src="https://agentmods.dev/badge/agents/josstei/maestro-orchestrate/performance-engineer/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/performance-engineer"><img src="https://agentmods.dev/badge/agents/josstei/maestro-orchestrate/performance-engineer.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.00221 | $0.00321 |
| Opus 5.5 | $0.00088 | $0.00128 |
| Sonnet 5.5 | $0.00044 | $0.00064 |
| Haiku 4.5 | $0.00022 | $0.00032 |
Grade A, and why
performance-engineer 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 10d 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: ["performance-engineer"]) 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.
- 10d ago First seen · 35 lines · 221 tokens per session scan A 4f4952c4259a
performance-engineer is an agent published in the GitHub repository josstei/maestro-orchestrate (484 stars, last pushed 5d ago), licensed Apache-2.0. It adds 221 tokens to every session and 321 once invoked, about $0.0009 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-10-07.
Other agents, from other repositories
db-performance-tuner
Database bottleneck specialist for the Hydraia pipeline. Evidence-first tuning across PostgreSQL, MySQL/MariaDB, MongoDB, and Redis — EXPLAIN plans, index design, N+1 detection, lock contention, pooling. Dispatched by the perf/DB route at design time. Read-only; proposes changes as plan tasks. NOT a Phase 5 reviewer…
perf-engineer
Performance diagnosis specialist for the Hydraia pipeline. Measurement-first — establishes a baseline, profiles, ranks bottlenecks by measured contribution, and proposes hypotheses with expected gains. Dispatched by the performance route at design time. Read-only; never edits source. NOT a Phase 5 reviewer (that is…
data-flow-timing-auditor
Cross-file data-flow timing and staleness: signals read before they settle, proxy gates, one-shot consumers snapshotting eventually-consistent state, init/hydration order, missed-event races.
code-archaeologist
Expert in legacy code, refactoring, and understanding undocumented systems.
debugger
Expert in systematic debugging, root cause analysis, and crash investigation. Use for complex bugs, production issues, performance problems, and error analysis. Triggers on bug, error, crash, not working, broken, investigate, fix.
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.