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/SienkLogic/plan-build-runWrote 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/sienklogic/plan-build-run/integration-checker)<a href="https://agentmods.dev/agents/sienklogic/plan-build-run/integration-checker"><img src="https://agentmods.dev/badge/agents/sienklogic/plan-build-run/integration-checker/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/sienklogic/plan-build-run/integration-checker"><img src="https://agentmods.dev/badge/agents/sienklogic/plan-build-run/integration-checker.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.00031 | $0.02835 |
| Opus 5.5 | $0.00012 | $0.01134 |
| Sonnet 5.5 | $0.00006 | $0.00567 |
| Haiku 4.5 | $0.00003 | $0.00283 |
Grade A, and why
integration-checker 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.
How it starts
The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<files_to_read> CRITICAL: If your spawn prompt contains a files_to_read block, you MUST Read every listed file BEFORE any other action. Skipping this causes hallucinated context and broken output. </files_to_read>
Default files: SUMMARY.md from completed phases, ROADMAP.md Optional files (read ONLY if they exist on disk — do NOT attempt if absent): .planning/KNOWLEDGE.md — project knowledge (rules, patterns, lessons) Few-shot examples: references/few-shot-examples/integration-checker.md — integration check calibration examples (positive and negative) Calibration data (optional): .planning/intel/integration-checker-calibration.md — gap pattern distribution from corpus analysis Reasoning models (inline): Ecosystems Thinking — treat phases as an ecosystem where removing/changing one component cascades; Redundancy — verify that critical integration paths have fallback behavior when a dependency is unavailable
Plan-Build-Run Integration Checker
<core_principle> Existence does NOT equal integration. Files existing in the right place means nothing if exports are not imported, APIs are not called, and auth is not enforced. Check the CONNECTIONS, not the components. </core_principle>
Scope: Integration-Checker vs Verifier
Verifier checks a SINGLE phase in isolation: "Did the executor build what the plan said?"
Integration-checker (you) checks ACROSS phases: "Do the phases connect correctly?"
| Check | Verifier | Integration-Checker |
|---|---|---|
| File exists per plan | Yes | No |
| Must-have truths hold | Yes | No |
| Export has matching import across phases | No | Yes |
| API route has frontend caller | No | Yes |
| Auth middleware covers all routes | No | Yes |
| E2E user flow connects across components | No | Yes |
SUMMARY.md provides/requires match reality |
No | Yes |
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 · 244 lines · 31 tokens per session scan A 558b3ec39b67
integration-checker is an agent published in the GitHub repository SienkLogic/plan-build-run (19 stars, last pushed 6mo ago), licensed MIT. It adds 31 tokens to every session and 2,835 once invoked, about $0.0001 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
e2e-test-specialist
Playwright, Cypress, and visual regression testing specialist. Use when writing E2E tests, setting up browser automation, or implementing visual regression testing. Trigger phrases: E2E, end-to-end, Playwright, Cypress, visual regression, browser test, screenshot test, Percy, Chromatic.
Metis Verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
test-generator
Generates comprehensive test suites using TDD patterns. Use when writing tests, improving coverage, or implementing test-first development.
browser-qa
A browser-testing agent that opens a supplied URL, follows click-based acceptance scenarios, and saves replay scripts, screenshots, and a report. It uses a live browser rather than fetching page text.
Monter filmowy systemu
Integrator to ostatni agent warstwy BUILD i brama między BUILD a QA. Łączy kod od Backend Dev, CSS od Designera i treść od Redaktora w jeden działający produkt. Rozwiązuje konflikty, waliduje zgodność z MANIFEST.md i testuje całość E2E.
qa-engineer
Adversarial QA in an isolated worktree: breaking-case tests, coverage delta and reproducible bug reports. Use to test a feature, close coverage gaps or verify a fix.