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/analytics_engineer)<a href="https://agentmods.dev/agents/josstei/maestro-orchestrate/analytics_engineer"><img src="https://agentmods.dev/badge/agents/josstei/maestro-orchestrate/analytics_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/analytics_engineer"><img src="https://agentmods.dev/badge/agents/josstei/maestro-orchestrate/analytics_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.00077 | $0.00200 |
| Opus 5.5 | $0.00031 | $0.00080 |
| Sonnet 5.5 | $0.00015 | $0.00040 |
| Haiku 4.5 | $0.00008 | $0.00020 |
Grade A, and why
analytics_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 1mo 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: ["analytics-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.
- 1mo ago First seen · 23 lines · 77 tokens per session scan A d8c1881a6f15
analytics_engineer is an agent published in the GitHub repository josstei/maestro-orchestrate (484 stars, last pushed 6d ago), licensed Apache-2.0. It adds 77 tokens to every session and 200 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
arcgentic-auditor
Dispatched when a round is in auditinprogress state. Produces a verdict file at the project's auditsdir following the canonical 9-section template, with a mechanically-verifiable fact table, structured findings, and lesson-codification result. Does NOT read planner/developer reasoning chains — audit independence is…
codex-reviewer
Runs a focused Codex code review with confidence-based filtering and source verification. Use for a second opinion on code changes, diffs, or architecture decisions.
security-reviewer
Audits WordPress PHP and JavaScript for security issues against the project's SECURITY.md checklist. Reports findings; never modifies code. Invoke before merging any PR or shipping a release.
logseq-format-reviewer
Read-only reviewer for logseq-brain skill prose. Use after editing any skills//SKILL.md or skills/shared/.md, before committing, to catch Logseq format violations in example output and description-trigger overlap between the five brain skills.
code-reviewer
Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.
oma-reviewer
Review one code section of at most 120 lines with concrete findings and explicit unknowns.