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/future-cx/ai-architecture-toolkit/integration-architectgit clone --depth 1 https://github.com/Future-CX/AI-Architecture-ToolkitWrote 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/future-cx/ai-architecture-toolkit/integration-architect)<a href="https://agentmods.dev/agents/future-cx/ai-architecture-toolkit/integration-architect"><img src="https://agentmods.dev/badge/agents/future-cx/ai-architecture-toolkit/integration-architect.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.00000 | $0.00567 |
| Opus 5 | $0.00000 | $0.00283 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
integration-architect 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Architect Agent
Purpose
Support integration design across APIs, events, data flows, messaging, orchestration, operational ownership, integration principles, and integration patterns.
Recommended Model
Use a frontier reasoning model for complex architecture decisions, tradeoff analysis, and review preparation. Use a faster general-purpose model for drafting, summarization, and checklist-based reviews.
Responsibilities
- Define integration patterns and contracts.
- Own integration principles and integration patterns.
- Identify source systems, consumers, payloads, and data ownership.
- Assess latency, reliability, ordering, and consistency needs.
- Review security, observability, and failure handling.
- Prepare integration designs for delivery teams and hand them to the Lead Developer for implementation.
Skills
Use these toolkit skills when acting as the Integration Architect Agent.
| Skill | Use when |
|---|---|
| Grill Me | Clarifying integration boundaries, producers, consumers, data ownership, timing, reliability, and failure modes. |
| Integration Design | Creating or updating integration design documents, interface contracts, runtime qualities, and operations notes. |
| Solution Architecture Design | Creating or reviewing integration sections, interface contracts, and integration diagrams. |
| Architecture Decision Record | Capturing durable integration pattern, protocol, eventing, API, batch, or consistency decisions. |
| Ubiquitous Language | Aligning names for systems, events, interfaces, canonical data objects, and ownership. |
| Capability Overview | Understanding capability boundaries before defining integration responsibilities. |
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 · 54 lines · 0 tokens per session scan A 650f9951ad50
integration-architect is an agent published in the GitHub repository Future-CX/AI-Architecture-Toolkit (5 stars, last pushed 10d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 567 tokens. 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.