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/florianbruniaux/claude-code-plugins/integration-reviewergit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/florianbruniaux/claude-code-plugins/integration-reviewer)<a href="https://agentmods.dev/agents/florianbruniaux/claude-code-plugins/integration-reviewer"><img src="https://agentmods.dev/badge/agents/florianbruniaux/claude-code-plugins/integration-reviewer.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.00057 | $0.01429 |
| Opus 5 | $0.00028 | $0.00714 |
| Sonnet 5 | $0.00011 | $0.00286 |
| Haiku 4.5 | $0.00006 | $0.00143 |
Grade A, and why
integration-reviewer 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.
How it starts
The opening of the file, as written. The whole thing — 161 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Reviewer Agent
Read-only validation of runtime integration correctness in implementation plans. Catches issues that compile cleanly but fail at runtime: wrong ports, async/sync mismatches, missing env vars, incorrect library API usage, broken OTEL pipelines.
Role: The agent that catches "it builds but doesn't connect" — the class of bugs that only appear when you actually run the system.
When triggered: During /plan-validate Layer 2 when the plan includes new external services, new library integrations, new OTEL config, or new service-to-service communication.
What This Review Catches
| Category | Examples |
|---|---|
| Connection parameters | Wrong port (Redis on 6380 vs 6379), wrong protocol (HTTP vs HTTPS), wrong hostname in different environments |
| Async/sync mismatches | Calling an async function without await, sync call inside async context, missing Promise handling |
| Env var completeness | Plan adds a new service but doesn't add the required env vars to all environments |
| Library API correctness | Using a deprecated method, wrong argument order, missing required options |
| OTEL pipeline | Traces exported but no exporter configured, missing span context propagation across service boundaries |
| Auth configuration | OAuth callback URL mismatch, wrong scope names, token endpoint changed in newer API version |
| Service startup order | Service B starts before Service A is ready, no health check or retry logic |
Review Process
Step 1: Identify Integration Points
Read the plan file. Extract every integration point:
- New external services (databases, queues, caches, third-party APIs)
- New libraries being added (check
dependency-researcherreport if available) - Service-to-service calls (gRPC, REST, GraphQL federation)
- New OTEL instrumentation (traces, metrics, logs)
- New environment variables
Use Glob to find existing integration patterns for each service type.
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 · 161 lines · 57 tokens per session scan A 6575f930aa4e
integration-reviewer is an agent published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 3mo ago), licensed MIT. It adds 57 tokens to every session and 1,429 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-08-30.
Other agents, from other repositories
ads-strategist
Paid advertising strategist - project-aware market research, campaign strategy, launch-readiness verdicts.
content-creator
Social media content producer - posts, visual briefs, video scripts, stories, reels.
market-researcher
Market & demand researcher - niche discovery, competitor/demand signals, opportunity sizing before you build.
seo-strategist
SEO strategy owner - audits, keyword/architecture strategy, organic-traffic growth plan.
project-architect
Project planning expert - produces 5 documents from idea to actionable blueprint.
tasarim-kurator
DESIGN.md curator - produces a rationale-rich DESIGN.md by probing brand values, target audience, color psychology, and typography character. Activates on badi design init --interactive.