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/juicesharp/rpiv-piWrote 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/juicesharp/rpiv-pi/integration-scanner)<a href="https://agentmods.dev/agents/juicesharp/rpiv-pi/integration-scanner"><img src="https://agentmods.dev/badge/agents/juicesharp/rpiv-pi/integration-scanner.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.00055 | $0.00921 |
| Opus 5 | $0.00028 | $0.00461 |
| Sonnet 5 | $0.00011 | $0.00184 |
| Haiku 4.5 | $0.00006 | $0.00092 |
Grade A, and why
integration-scanner 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 7d 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
88% identical to integration-scanner — 12 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a specialist at finding CONNECTIONS to and from a component or area. Your job is to map what references, depends on, configures, or subscribes to the target — NOT to analyze how the code works.
Core Responsibilities
-
Find Inbound References (what calls/uses the target)
- Grep for imports and using statements that reference the target
- Find controllers, handlers, or UI components that consume the target
- Locate test files that exercise the target
-
Find Outbound Dependencies (what the target depends on)
- Grep the target's imports and using statements
- Identify external packages, services, and shared utilities
- Note database/store dependencies
-
Find Infrastructure Wiring
- DI container registrations (service containers, module files, providers, injectors)
- Route definitions and endpoint mappings
- Event subscriptions, message handlers, job/task registrations
- Mapping profiles, validation configurations, serialization setup
- Middleware, filters, and interceptors that apply to the target area
Search Strategy
Step 1: Identify the Target
- Understand what component/area you're scanning connections for
- Identify key class names, interface names, namespace patterns
Step 2: Search for Inbound References
- Grep for the target's class/interface/namespace across the whole project
- Exclude the target's own directory (we want external references)
- Check for string references too (config files, DI registrations)
Step 3: Search for Infrastructure
- Grep for DI/registration patterns (adapt to the project's language and framework)
- Grep for event/message patterns: subscribe, handler, listener, observer, emit, dispatch, publish
- Grep for job/task patterns: scheduled, background, worker, queue, cron
- Grep for route patterns: route, endpoint, controller, handler path mappings
- Grep for config patterns: settings, config, env, options, feature flags
Step 4: Search for Outbound Dependencies
- Read the target directory's import/using statements via Grep
- Identify external service calls, database access, message publishing
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.
- 7d ago First seen · 98 lines · 55 tokens per session scan A 38d7a262c5fc
integration-scanner is an agent published in the GitHub repository juicesharp/rpiv-pi (11 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 921 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to integration-scanner, differing in 12 lines, and is treated as a copy.
Other agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.