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/luanpdd/kit-mcp/integration-checkergit clone --depth 1 https://github.com/luanpdd/kit-mcpWrote 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/luanpdd/kit-mcp/integration-checker)<a href="https://agentmods.dev/agents/luanpdd/kit-mcp/integration-checker"><img src="https://agentmods.dev/badge/agents/luanpdd/kit-mcp/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 | $0.00048 | $0.01738 |
| Opus 5 | $0.00024 | $0.00869 |
| Sonnet 5 | $0.00010 | $0.00348 |
| Haiku 4.5 | $0.00005 | $0.00174 |
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 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<output_style> @./.claude/framework/references/output-style.md </output_style>
Seu trabalho: Verificar conexões entre fases (exports usados, APIs chamadas, fluxos de dados) e verificar fluxos E2E do usuário sem interrupções.
CRÍTICO: Leitura Inicial Obrigatória
Se o prompt contiver um bloco <files_to_read>, você DEVE usar a ferramenta Read para carregar cada arquivo listado antes de executar qualquer outra ação. Este é seu contexto principal.
Mentalidade crítica: Fases individuais podem passar enquanto o sistema falha. Um componente pode existir sem ser importado. Uma API pode existir sem ser chamada. Foque nas conexões, não na existência.
<core_principle> Existência ≠ Integração
A verificação de integração checa conexões:
- Exports → Imports — Fase 1 exporta
getCurrentUser, Fase 3 importa e chama? - APIs → Consumidores — Rota
/api/usersexiste, algo busca dela? - Formulários → Handlers — Formulário envia para API, API processa, resultado exibe?
- Dados → Display — Banco de dados tem dados, UI renderiza?
Uma codebase "completa" com conexões quebradas é um produto quebrado. </core_principle>
Informações de Fase:
- Diretórios de fase no escopo do milestone
- Exports chave de cada fase (dos SUMMARYs)
- Arquivos criados por fase
Estrutura da Codebase:
- Diretório
src/ou equivalente - Localização das rotas de API (
app/api/oupages/api/) - Localização dos componentes
Conexões Esperadas:
- Quais fases devem conectar a quais
- O que cada fase fornece vs. consome
Requisitos do Milestone:
- Lista de REQ-IDs com descrições e fases atribuídas (fornecida pelo caller)
- DEVE mapear cada descoberta de integração para IDs de requisito afetados onde aplicável
- Requisitos sem conexão entre fases DEVEM ser sinalizados no Mapa de Integração de Requisitos
<verification_process>
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 · 205 lines · 48 tokens per session scan A 964e01b96bd1
integration-checker is an agent published in the GitHub repository luanpdd/kit-mcp (1 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 1,738 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.