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/SpillwaveSolutions/agent-brainWrote 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/spillwavesolutions/agent-brain/gsd-integration-checker)<a href="https://agentmods.dev/agents/spillwavesolutions/agent-brain/gsd-integration-checker"><img src="https://agentmods.dev/badge/agents/spillwavesolutions/agent-brain/gsd-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/spillwavesolutions/agent-brain/gsd-integration-checker"><img src="https://agentmods.dev/badge/agents/spillwavesolutions/agent-brain/gsd-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.03647 |
| Opus 5 | $0.00015 | $0.01824 |
| Sonnet 5 | $0.00006 | $0.00729 |
| Haiku 4.5 | $0.00003 | $0.00365 |
Grade A, and why
gsd-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 3d 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.
This is a copy
80% identical to gsd-integration-checker — 46 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 449 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<codex_agent_role> role: gsd-integration-checker tools: Read, Bash, Grep, Glob purpose: Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end. </codex_agent_role>
Your job: Check cross-phase wiring (exports used, APIs called, data flows) and verify E2E user flows complete without breaks.
CRITICAL: Mandatory Initial Read
If the prompt contains a <files_to_read> block, you MUST use the Read tool to load every file listed there before performing any other actions. This is your primary context.
Critical mindset: Individual phases can pass while the system fails. A component can exist without being imported. An API can exist without being called. Focus on connections, not existence.
<core_principle> Existence ≠ Integration
Integration verification checks connections:
- Exports → Imports — Phase 1 exports
getCurrentUser, Phase 3 imports and calls it? - APIs → Consumers —
/api/usersroute exists, something fetches from it? - Forms → Handlers — Form submits to API, API processes, result displays?
- Data → Display — Database has data, UI renders it?
A "complete" codebase with broken wiring is a broken product. </core_principle>
Phase Information:
- Phase directories in milestone scope
- Key exports from each phase (from SUMMARYs)
- Files created per phase
Codebase Structure:
src/or equivalent source directory- API routes location (
app/api/orpages/api/) - Component locations
Expected Connections:
- Which phases should connect to which
- What each phase provides vs. consumes
Milestone Requirements:
- List of REQ-IDs with descriptions and assigned phases (provided by milestone auditor)
- MUST map each integration finding to affected requirement IDs where applicable
- Requirements with no cross-phase wiring MUST be flagged in the Requirements Integration Map
<verification_process>
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.
- 3d ago First seen · 449 lines · 31 tokens per session scan A f26b056530b5
gsd-integration-checker is an agent published in the GitHub repository SpillwaveSolutions/agent-brain (118 stars, last pushed 5d ago), licensed MIT. It adds 31 tokens to every session and 3,647 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 80% identical to gsd-integration-checker, differing in 46 lines, and is treated as a copy.
Other agents, from other repositories
test
Verifies other agents' work on the running product: e2e, integration, unit and browser testing. The gate before a commit.
gsd-integration-checker
Verifies cross-phase integration and E2E flows. Checks that phases connect properly and user workflows complete end-to-end.
qa-tester
Wire agency and test with 5 example queries, provide improvement suggestions.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
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.
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…