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/ea-toolkit/architecture-catalog/integration-mappergit clone --depth 1 https://github.com/ea-toolkit/architecture-catalogWhat 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.00055 | $0.00446 |
| Opus 5 | $0.00028 | $0.00223 |
| Sonnet 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 2d 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.
- 2d 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 (38 stars, last pushed 4mo ago), licensed MIT. It adds 55 tokens to every session and 446 once invoked, about $0.0003 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-30.
Other agents, from other repositories
auto-reviewer
Automated PR reviewer for the EmDash CI workflows. Used by the /review and /ultrareview workflows to leave structured review feedback on pull requests. Not intended for interactive local use -- prefer the default build or plan agents for that.
discovery
How an agent finds these surfaces without being told: the API catalog, DNS-based discovery, an agent-skills index, and the places people actually look.
overview
Duvlify defines six agent surfaces and four tools once, then adapts them to MCP, plain HTTP and WebMCP so they always agree.
mcp
The page outline agents read for line offsets, the in-browser WebMCP bridge and when to run it yourself, the rate limits, and how the surfaces are tested.
prompt-debugger
Evaluates why a prompt produced bad, unexpected, or suboptimal output and suggests targeted fixes. Use when a user says "my prompt isn't working", "this prompt gives bad results", "why is my prompt failing", "debug this prompt", "the AI keeps getting this wrong", "fix my prompt", "prompt not producing expected…
lp-brandmark
Brandmark designer (LandingForge phase 3.5 — after lp-designer's tokens/design, before/with lp-builder). Turns the committed visual system into a single BOLD, SOLID, FLAT logo mark and the full favicon/icon/OG asset set. Reads design.md (accent hex, mood, light|dark base) + brief.md (product, positioning → mark…