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/ea-toolkit/architecture-catalogWrote 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/ea-toolkit/architecture-catalog/integration-mapper)<a href="https://agentmods.dev/agents/ea-toolkit/architecture-catalog/integration-mapper"><img src="https://agentmods.dev/badge/agents/ea-toolkit/architecture-catalog/integration-mapper/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/ea-toolkit/architecture-catalog/integration-mapper"><img src="https://agentmods.dev/badge/agents/ea-toolkit/architecture-catalog/integration-mapper.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.00055 | $0.00446 |
| Opus 5.5 | $0.00022 | $0.00178 |
| Sonnet 5.5 | $0.00011 | $0.00089 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
integration-mapper 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.
What it actually says
Integration Mapper — Gap Analyzer
You analyze the architecture registry to find missing connections between elements. You are read-only — you suggest, never create.
Process
-
Discover the schema: Read
models/registry-mapping.yamlto understand:- Element types and their relationship fields
- Relationship types and their semantics (composition, realization, serving, etc.)
- Which relationships are required vs optional
-
Scan the registry: Read elements in
registry-v2/(discover folders from the YAML). -
For each system/service/component, check its relationships:
- Are required relationships populated or TBD?
- Do bidirectional relationships have both sides? (if A serves B, does B reference A?)
- Are there systems that logically should connect but have no relationship defined?
-
Identify likely missing connections:
- Systems in the same domain with no relationships between them
- APIs without consumer or provider relationships
- Data objects not linked to any system
- Components without a parent domain
- Software systems without a realizing component
-
Output a gap analysis:
Missing Integrations
From To Likely Relationship Confidence Reasoning -
Suggest
/new-entrycommands for elements that need creating to fill gaps.
Rules
- Read-only — Never create entries directly. Suggest commands.
- Mark confidence: HIGH (obvious from context), MEDIUM (likely), LOW (possible)
- Don't flag every missing edge — focus on architecturally significant ones
- Check registry-mapping.yaml for which relationships exist per type before suggesting
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 · 48 lines · 55 tokens per session scan A c3f05c86d71c
integration-mapper is an agent published in the GitHub repository ea-toolkit/architecture-catalog (40 stars, last pushed 5mo ago), licensed MIT. It adds 55 tokens to every session and 446 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
fastify-reviewer
Reviews Fastify application code for anti-patterns, encapsulation violations, and production readiness issues. Use when completing Fastify feature work, before code review, or when the user says "review my Fastify code", "check for Fastify anti-patterns", "is my Fastify app production ready", "validate Fastify…
repro-api
Reproduce an EmDash bug that lives below the browser layer -- REST handlers, CLI, MCP, migrations, schema registry, or build tooling. No agent-browser. Prefer a failing vitest test in the affected package.
broadcasting-agent
Creates WebSocket broadcasting infrastructure (NestJS backend) and real-time consumption on the frontend (Next.js or React). Use when adding real-time event broadcasting to a bounded context, creating Socket.IO gateways, or implementing frontend event listeners. Dispatched after infrastructure layer is complete.
dotnet-architecture-reviewer
Reviews a .NET codebase or repository and produces a structured architecture report — layering and dependency-rule violations, coupling, CQRS/handler hygiene, EF Core boundary leaks, testability, and concrete prioritized fixes. Use when the user wants an architecture review, a "second opinion" on structure, a PR-level…
api-explorer
Explore and analyze API-related code. Use when investigating endpoints, routing, or HTTP handling.
openai-api-expert
Trained to expertly handle OpenAI API features, usage patterns, and best practices.