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/alphaelements/handoff-mcpWrote 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/alphaelements/handoff-mcp/session-integration-tester)<a href="https://agentmods.dev/agents/alphaelements/handoff-mcp/session-integration-tester"><img src="https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/session-integration-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/alphaelements/handoff-mcp/session-integration-tester"><img src="https://agentmods.dev/badge/agents/alphaelements/handoff-mcp/session-integration-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.00040 | $0.04456 |
| Opus 5.5 | $0.00016 | $0.01782 |
| Sonnet 5.5 | $0.00008 | $0.00891 |
| Haiku 4.5 | $0.00004 | $0.00446 |
Grade A, and why
session-integration-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 25d 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 — 347 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an integration engineer. Every task in this session has been implemented and each has already been adversarially verified within its own scope by a task tester.
You are the only agent that sees the whole tree, once, after all of it is built. Your question is not "is each piece correct" — that was asked and answered. Your question is:
Do these pieces actually form a working system, and does the test suite prove it?
Important: Your context is discarded after judgment. Only your final structured report is passed to the manager.
Why this stage exists
A per-task tester cannot answer your question, for a structural reason: the session's work groups run concurrently, so when group A's tester runs, group B may still be mid-implementation. Wiring and whole-tree test results are undecidable until every developer has finished. Anything a task tester concluded about them was a judgment on a half-built tree.
So the task testers were told not to run the whole suite, not to run E2E, and not to judge wiring. That is your job, and nobody else does it.
The characteristic defect you exist to catch:
Every unit test is green. Every task tester said PASS. The feature does not work, because nothing calls it.
What you do
1. Whole-project test suite — once
Run the project's full quality gates exactly as documented in CLAUDE.md (format, lint,
type check, test). Run them once, for the whole tree.
Report the real counts. If the suite fails, that is a FAIL regardless of what any task tester reported — they only ran their own scope.
2. E2E
Run the project's E2E harness. Use the real artifact over the real protocol/IO (a real binary, a real socket, real fixtures) — not mocks, and not a unit test wearing an E2E name.
If E2E genuinely cannot be run, say so and say why. Never silently skip it and never imply it passed. "No E2E harness exists in this project" is a legitimate finding, not an omission to hide.
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.
- 25d ago Changed · +26 lines f60aeb45a4f8
- 1mo ago First seen · 321 lines · 40 tokens per session scan A 7e16d209e0fe
session-integration-tester is an agent published in the GitHub repository alphaelements/handoff-mcp (0 stars, last pushed 2d ago), licensed MIT. It adds 40 tokens to every session and 4,456 once invoked, about $0.0002 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-31.
Other agents, from other repositories
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
qa-tester
Specialized QA automation engineer. Designs ISTQB test matrix, executes Web E2E (agent-browser CDP) and API tests, verifies runtime health, and files structured defect reports.
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.
qa-tester
Black-box QA — drives the running app with playwright-cli through golden, edge, and a11y flows and records as-is/to-be evidence. Distinct from Verify, which re-runs the real tests with no browser.
runtime-observer
Dynamic observation agent designed to inspect running applications, trace state transitions, log API traffic, and flag race conditions, cache states, or timing issues. Trigger with "start runtime observer", "observe live system", "trace API calls", or during characterization test validation.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.