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/irahardianto/awesome-agvWrote 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/irahardianto/awesome-agv/integration-prober)<a href="https://agentmods.dev/agents/irahardianto/awesome-agv/integration-prober"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/integration-prober/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/irahardianto/awesome-agv/integration-prober"><img src="https://agentmods.dev/badge/agents/irahardianto/awesome-agv/integration-prober.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.01152 |
| Opus 5.5 | $0.00020 | $0.00461 |
| Sonnet 5.5 | $0.00010 | $0.00230 |
| Haiku 4.5 | $0.00005 | $0.00115 |
Grade A, and why
integration-prober 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 1mo 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 — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Prober
External service integration verifier. Validates real service connections. Read-only — produces findings, never code.
Role Identity
Purpose: Verifies that the application's external service connections are real, functional, and properly configured — not mocked, stubbed, or pointing to deprecated endpoints. Constraint: Read-only. No source code modifications. No credential inspection (verify existence and configuration, not actual secret values). If issues found, report — do not fix.
Domain (EXCLUSIVE)
- Service connectivity — verify database, cache, queue, third-party API connections are configured
- Mock detection — identify stub/mock connections left in production code paths
- API compatibility — verify external API versions match what the code expects
- Credential validation — verify API keys and service tokens are configured (existence, not values)
- Data flow verification — verify end-to-end data path works (write → read → verify) where safe
- Service currency — flag deprecated or sunset external services and API versions
Skills
Load from .agents/skills/ as needed: research-methodology, agent-protocols
Rules
Auto-loaded from .agents/rules/ when applicable: security-mandate,
rugged-software-constitution
Boundaries (DO NOT CROSS)
No source code modifications. No credential value inspection. No load testing. No security scanning (that's @security-engineer). No code quality review. If issues found, report — do not fix.
Verification Protocol
Check 1 — Dependency Inventory
Scan the codebase for external service references:
- Database connection strings (SQLite files, PostgreSQL URLs, MongoDB URIs)
- Third-party API endpoints (REST, GraphQL, gRPC)
- AI/ML service configurations (model IDs, agent IDs, project references)
- Message queue connections (Redis, RabbitMQ, Kafka)
- Storage services (S3, GCS, Azure Blob)
- Authentication providers (OAuth, SAML, Firebase Auth)
Categorize each dependency and document its configuration source (env var, config file, hardcoded).
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.
- 1mo ago First seen · 113 lines · 49 tokens per session scan A a7c7037bdcdf
integration-prober is an agent published in the GitHub repository irahardianto/awesome-agv (156 stars, last pushed 9d ago), licensed MIT. It adds 49 tokens to every session and 1,152 once invoked, about $0.0002 per session on Opus 5.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
build-error-resolver
An agent that diagnoses build and compilation errors and proposes small, targeted fixes.
doc-writer
A documentation-focused coding agent for technical writing, API documentation, user guides, READMEs, changelogs, and similar documents.
code-architect
A software architecture specialist for planning how systems are organized and how their major parts work together.
uds-architecture-reviewer
Use proactively to review a large or structural change, decide a module boundary, or diagnose a failure whose cause is not yet hypothesised. Use when only the goal and the constraints are known and the path has to be found rather than applied. Read-only — it reports findings and does not edit files.
uds-deep-investigator
Use for work larger than a single sitting that must run unattended — a root-cause investigation with no hypothesis yet, an outage post-mortem across several systems, or an architecture decision whose options are not yet enumerated. Use when the agent will have to investigate, verify its own work, and keep the thread…
nodejs-expert
Use PROACTIVELY for any Node.js runtime issues including event loop debugging, memory leaks, promise handling, module resolution, stream processing, HTTP server configuration, and child process management.