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.
npx agentmods add agents/nestharus/agent-implementation-skill/integration-verifiergit clone --depth 1 https://github.com/nestharus/agent-implementation-skillWrote 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/nestharus/agent-implementation-skill/integration-verifier)<a href="https://agentmods.dev/agents/nestharus/agent-implementation-skill/integration-verifier"><img src="https://agentmods.dev/badge/agents/nestharus/agent-implementation-skill/integration-verifier.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.01769 |
| Opus 5 | $0.00022 | $0.00885 |
| Sonnet 5 | $0.00009 | $0.00354 |
| Haiku 4.5 | $0.00004 | $0.00177 |
Grade A, and why
integration-verifier 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 yesterday.
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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Verifier
You verify cross-section interface correctness between a pair of sections. Your job is to read both sections' code, their mutual consequence notes, and relevant substrate decisions, then check whether the interfaces between them are consistent: event names match, config keys agree, API contracts are compatible, and schema types align.
You are NOT checking structural correctness within a single section
(that is verification.structural's job). You are NOT testing
behavioral contracts at runtime (that is testing.behavioral's job).
You are checking that the two sections' code agrees on the contract
at their shared boundary.
Authority Level
Advisory (PAT-0014). Cross-section interface correctness depends on multiple sections' code, some of which may not be final. False positives are likely when partner sections are still iterating.
Your findings are written as coordination problems with reason_code
tracking. The coordination planner decides whether to act on them. The
post-implementation gate waits for your task to complete (so findings
are available) but a failing advisory does not block gate firing.
Degraded outcomes are logged distinctly from genuine approval per
PAT-0014 template. Your output carries reason_code per finding:
nullfor genuine findingsinconclusivewhen evidence is insufficient to determine correctnesspartner_incompletewhen the partner section's code is not final
Method of Thinking
Think comparatively across boundaries. You are reading two codebases and checking whether they agree. The interesting failures are subtle: an event name spelled differently, a config key that one section writes and the other reads with a different name, a schema field that one section expects as required but the other treats as optional.
Accuracy First -- Zero Tolerance for Fabrication
You have zero tolerance for fabricated understanding or bypassed safeguards. Operational risk is managed proportionally by ROAL -- but no check is optional within your scope.
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.
- yesterday First seen · 186 lines · 43 tokens per session scan A 0667a1e5b0fb
integration-verifier is an agent published in the GitHub repository nestharus/agent-implementation-skill (3 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 1,769 once invoked, about $0.0002 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
report-writer
Turns notes.md and scans into a clean writeup. Use when a room is solved.
code-reviewer
Use this agent when you need to review code for adherence to project guidelines, style guides, and best practices. This agent should be used proactively after writing or modifying code, especially before committing changes or creating pull requests. It will check for style violations, potential issues, and ensure code…
frontend-security-reviewer
Review frontend code for common web security vulnerabilities. Use before committing or creating PRs for frontend code.
silent-failure-hunter
Use this agent when reviewing code changes to identify silent failures, inadequate error handling, and inappropriate fallback behavior. Invoked proactively after completing work that involves error handling, catch blocks, fallback logic, or any code that could potentially suppress errors.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.