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/integration-engineer)<a href="https://agentmods.dev/agents/josstei/maestro-orchestrate/integration-engineer"><img src="https://agentmods.dev/badge/agents/josstei/maestro-orchestrate/integration-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/integration-engineer"><img src="https://agentmods.dev/badge/agents/josstei/maestro-orchestrate/integration-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.00105 | $0.00208 |
| Opus 5.5 | $0.00042 | $0.00083 |
| Sonnet 5.5 | $0.00021 | $0.00042 |
| Haiku 4.5 | $0.00011 | $0.00021 |
Grade A, and why
integration-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 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: ["integration-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.
- today Changed · -20 lines · -207 tokens per session 722671332071
- 1mo ago First seen · 40 lines · 312 tokens per session scan A 3e785e391230
integration-engineer is an agent published in the GitHub repository josstei/maestro-orchestrate (486 stars, last pushed today), licensed Apache-2.0. It adds 105 tokens to every session and 208 once invoked, about $0.0004 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
critic-security
Review code for OWASP-style security issues (injection, authn/authz, secrets, supply chain, LLM-specific) in parallel with other critics during /vdd-multi. For full audits producing a formal docs/audit/ report, use security-auditor instead.
architecture-reviewer
Review docs/ARCHITECTURE.md for Data Model correctness, Security (OWASP), Scalability, and YAGNI. Spawn after architect to gate the Architecture→Planning boundary.
docs-engineer
Documentation specialist for the Hydraia pipeline. Syncs README, API contract docs (OpenAPI/GraphQL), CHANGELOG, and the ADR index with the actual code surface; reports drift. Runs in Phase 6 (updates, never blocks) and on demand via /hydraia:docs. Never invents API behavior.
backend-specialist
Expert backend architect for Node.js, Python, and modern serverless/edge systems. Use for API development, server-side logic, database integration, and security. Triggers on backend, server, api, endpoint, database, auth.
documentation-writer
Expert in technical documentation. Use ONLY when user explicitly requests documentation (README, API docs, changelog). DO NOT auto-invoke during normal development.
workflow-subagent
Generic stage executor for the stagent plugin. Launched by the main agent for any subagent-typed stage in a workflow. Self-resolves its stage context from state.md via subagent-bootstrap.sh — does NOT rely on the main agent's prompt for path / epoch / input data. Then follows the stage's canonical instructions file…