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 skills/davidroliverba/architectkb/integrationnpx skills add DavidROliverBA/ArchitectKB --skill integrationgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/skills/davidroliverba/architectkb/integration)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/integration"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/integration.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.01603 |
| Opus 5 | $0.00000 | $0.00801 |
| Sonnet 5 | $0.00000 | $0.00321 |
| Haiku 4.5 | $0.00000 | $0.00160 |
Grade A, and why
integration 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 4d 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/integration
Create an Integration note documenting how two systems exchange data, including pattern, protocol, frequency, SLA, and error handling.
Usage
/integration <source-system> <target-system>
/integration SAP DataPlatform
/integration DataPlatform Snowflake --pattern batch
/integration "System - SAP S/4HANA" "System - DataPlatform" --frequency hourly
Instructions
Creates comprehensive Integration notes linking System notes and documenting connection characteristics.
Phase 1: Parse Input & Validate Systems
- Extract source and target system names
- Search vault for both systems:
node scripts/graph-query.js --type System --search "<source>" node scripts/graph-query.js --type System --search "<target>" - If systems not found:
- "[[System - {{name}}]] not found. Create it first? (Y/n)"
- Offer to create System notes before Integration
- If system already integrates, show existing:
- "Found: [[Integration - SAP to DataPlatform]]. Edit instead? (Y/n)"
Phase 2: Essential Information
Gather required fields:
Creating Integration: {{source}} → {{target}}
1️⃣ Integration Pattern:
- api-sync (REST/GraphQL synchronous)
- event-streaming (Kafka/Pub-Sub asynchronous)
- batch-etl (scheduled bulk data transfer)
- message-queue (queued messages with processing)
- file-transfer (SFTP/S3 file exchange)
- database-replication (direct DB sync)
Default: api-sync
User input: [selection]
2️⃣ Protocol:
(Based on pattern selection, suggest defaults)
- For api-sync: rest, graphql, soap, odata
- For event-streaming: kafka, rabbitmq, pubsub
- For batch-etl: s3, sftp, sql
Default: [depends on pattern]
User input: [selection]
3️⃣ Frequency:
- real-time (< 1 second latency)
- near-real-time (< 5 minutes)
- hourly
- daily
- weekly
- on-demand
Default: daily
User input: [selection]
4️⃣ Direction:
- one-way (source → target only)
- bidirectional (source ↔ target)
Default: one-way
User input: [selection]
5️⃣ Criticality:
- critical (business stops if fails)
- high (significant impact)
- medium (moderate impact)
- low (minimal impact)
Default: medium
User input: [selection]
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.
- 4d ago First seen · 253 lines · 0 tokens per session scan A 57d8e92e4fd4
integration is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,603 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…