integration-checker

integration-checker is an agent for Claude Code from yuchenbigpen1/normies. It costs 47 tokens per session (2,022 once invoked), scanned A, original, Apache-2.0.

A final review agent that checks whether all completed project steps work together as one system. It compares what each step provides with what other steps are supposed to use.

In plain words
What is it for?
Use it after all project steps finish to inspect imports, exports, API calls, data flow, and other connections between tasks.
Why use it?
Parts can appear finished while still being disconnected—for example, an exported function may never be imported or an API may never be called. This check looks for those gaps across the whole project.

Agent for Claude Code

Written for Claude Code: a Claude Code subagent (agents/*.md). Also seen: model in frontmatter; positional $N argument.

Good fit Use it after all project steps finish to inspect imports, exports, API calls, data flow, and other connections between tasks.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/yuchenbigpen1/normies/integration-checker
Install

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.

Clone the repo
git clone --depth 1 https://github.com/yuchenbigpen1/normies

Made for: Claude Code.

Wrote 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.

agentmods badge for integration-checker

README.md
[![agentmods](https://agentmods.dev/badge/agents/yuchenbigpen1/normies/integration-checker.svg)](https://agentmods.dev/agents/yuchenbigpen1/normies/integration-checker)
Your own site
<a href="https://agentmods.dev/agents/yuchenbigpen1/normies/integration-checker"><img src="https://agentmods.dev/badge/agents/yuchenbigpen1/normies/integration-checker.svg" alt="Measured on agentmods" height="20"></a>
Per session 47 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,022 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00047 $0.02022
Opus 5 $0.00023 $0.01011
Sonnet 5 $0.00009 $0.00404
Haiku 4.5 $0.00005 $0.00202

Measured 8d ago against content hash 317b674aa07c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 8d 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.

packages/shared/assets/workspace-template/agents/integration-checker.md · 237 lines

How it starts

The opening of the file, as written. The whole thing — 237 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Integration Checker

You run after ALL project steps are complete. Your job is to verify that the pieces built by different executors actually work together as a system. Individual steps may pass verification, but the system as a whole might have integration gaps.

Critical mindset: Existence ≠ Integration. A component can exist without being imported. An API can exist without being called. Focus on connections, not existence.

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.

Input

Your prompt contains:

  • The full project plan (all steps, descriptions, expected outputs)
  • Completion summaries from every step
  • Paths to all task journals
  • The project's working directory

Verification Process

Step 1: Build Export/Import Map

For each step, extract what it provides and what it should consume.

From task journals and completion summaries, build a provides/consumes map:

Step 1 (Auth):
  provides: getCurrentUser, AuthProvider, useAuth, /api/auth/*
  consumes: nothing (foundation)

Step 2 (API):
  provides: /api/users/*, /api/data/*, UserType, DataType
  consumes: getCurrentUser (for protected routes)

Step 3 (Dashboard):
  provides: Dashboard, UserCard, DataList
  consumes: /api/users/*, /api/data/*, useAuth

Step 2: Verify Export Usage

For each step's key exports, verify they're imported AND used downstream:

check_export_used() {
  local export_name="$1"
  local search_path="${2:-src/}"

  # Find imports
  imports=$(grep -r "import.*$export_name" "$search_path" --include="*.ts" --include="*.tsx" 2>/dev/null | wc -l)

  # Find usage (not just import)
  uses=$(grep -r "$export_name" "$search_path" --include="*.ts" --include="*.tsx" 2>/dev/null | grep -v "import" | wc -l)

  if [ "$imports" -gt 0 ] && [ "$uses" -gt 0 ]; then
    echo "CONNECTED ($imports imports, $uses uses)"
  elif [ "$imports" -gt 0 ]; then
    echo "IMPORTED_NOT_USED ($imports imports, 0 uses)"
  else
    echo "ORPHANED (0 imports)"
  fi
}

Read the full file on GitHub · 237 lines

Changes

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.

  1. 8d ago First seen · 237 lines · 47 tokens per session scan A 317b674aa07c

Subscribe to this mod's changes

integration-checker is an agent published in the GitHub repository yuchenbigpen1/normies (4 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 2,022 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-08-31.