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/yuchenbigpen1/normiesWrote 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/yuchenbigpen1/normies/integration-checker)<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>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.00047 | $0.02022 |
| Opus 5 | $0.00023 | $0.01011 |
| Sonnet 5 | $0.00009 | $0.00404 |
| Haiku 4.5 | $0.00005 | $0.00202 |
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.
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
}
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.
- 8d ago First seen · 237 lines · 47 tokens per session scan A 317b674aa07c
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.
Other agents, from other repositories
e2e-test-generator
Generate and run Playwright e2e tests — Page Object Model, stable selectors, network mocking, multi-viewport coverage.
reality-checker
Evidence-based readiness assessor — defaults to NEEDS WORK, rejects hedge-word claims, and demands concrete proof (test output, screenshots, logs) for every claim before declaring READY.
gan-evaluator
Runs Playwright against gan-generator's output, scores against the plan's rubric, returns concrete failures. Step 3 of 3 in GAN harness — the adversarial verification step.
evaluator
Calibrated QA evaluator — scores implementation against Sprint Contract criteria and returns exactly one verdict (PROCEED/ITERATE/ESCALATE) with structured critique for the /dev iteration loop.
test-generator
Generate and run tests matching the project's existing test conventions — table-driven, edge-case checklist, multi-stack aware (Go/TS/Python/Rust).
gan-generator
Implements features against a gan-planner plan. Writes code + Playwright tests in lockstep, ensures anti-slop checklist is clean. Step 2 of 3 in GAN harness.