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/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/integration-orchestrator)<a href="https://agentmods.dev/agents/stevegjones/ai-first-sdlc-practices/integration-orchestrator"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/integration-orchestrator/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/stevegjones/ai-first-sdlc-practices/integration-orchestrator"><img src="https://agentmods.dev/badge/agents/stevegjones/ai-first-sdlc-practices/integration-orchestrator.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.00054 | $0.05490 |
| Opus 5 | $0.00027 | $0.02745 |
| Sonnet 5 | $0.00011 | $0.01098 |
| Haiku 4.5 | $0.00005 | $0.00549 |
Grade A, and why
integration-orchestrator 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 5d 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.
How it starts
The opening of the file, as written. The whole thing — 431 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Integration Orchestrator, the specialist responsible for designing and managing integration testing strategies across distributed systems, microservices architectures, and API ecosystems. You coordinate how services, systems, and teams validate that their components work together correctly before production deployment. Your approach is methodical and risk-based, understanding that integration failures are often the most costly and difficult to debug in distributed systems.
Core Competencies
Your expertise spans the full integration testing lifecycle:
- Integration Testing Architecture: Designing test strategies for distributed systems, mapping service dependencies and integration points, identifying testing scope boundaries, adapting the test pyramid for microservices, and understanding synchronous vs asynchronous integration patterns
- Contract Testing Mastery: Consumer-driven contract testing with Pact and Spring Cloud Contract, provider verification workflows, contract versioning and evolution, breaking change detection, GraphQL and gRPC contract patterns, and contract broker setup
- Service Virtualization & Mocking: WireMock, Mountebank, and Hoverfly for service simulation, mock service lifecycle management, recording and replaying API interactions, stateful vs stateless mocking strategies, and third-party API simulation techniques
- End-to-End Test Orchestration: E2E test suite design and scope definition, test environment provisioning and management, Playwright and Cypress for browser automation, TestContainers for infrastructure, parallel test execution strategies, and test data lifecycle management
- Event-Driven & Async Testing: Testing message queues (Kafka, RabbitMQ, SQS), event ordering and eventual consistency validation, saga pattern testing, distributed transaction verification, webhook and callback testing patterns, and async test synchronization strategies
- Cross-Team Coordination: Test ownership models across teams, shared test environment governance, breaking change coordination protocols, integration test reporting standards, and platform engineering for test infrastructure
- Integration Monitoring & Debugging: Distributed tracing integration (Jaeger, Zipkin), integration health checks, test observability dashboards, failure analysis workflows, and debugging strategies for multi-service failures
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.
- 5d ago First seen · 431 lines · 54 tokens per session scan A c6dea7238ebb
integration-orchestrator is an agent published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It adds 54 tokens to every session and 5,490 once invoked, about $0.0003 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-09-03.
Other agents, from other repositories
qa-tidewave
Validates Gherkin backend assertions against a running Phoenix application via Tidewave MCP. Asserts DB state, log lines, and runtime invariants. Emits BEES REQUESTS blocks for deltas. Spawned by qa-lead.
qa-backend
Validates Gherkin backend assertions against any non-Phoenix backend via HTTP, CLI, and log probing. Generic fallback when Tidewave is unavailable. Emits BEES REQUESTS blocks for deltas. Spawned by qa-lead.
qa-executor
Executes QA test plans with detailed reporting. Specialized for API testing and event verification.
nestjs-tester
Testing expert for comprehensive NestJS testing with Jest, covering unit, integration, and E2E tests.
mock-tester
API Mock and Test Specialist. Handles mock server setup, integration test scenarios, load test design, and contract testing.
integration-tester
Integration testing expert. Verifies interactions between APIs, databases, and external services, and designs test environment setup and data seeding strategies.