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 skills add The-AI-Directory-Company/agents-and-skills --skill integration-specificationgit clone --depth 1 https://github.com/The-AI-Directory-Company/agents-and-skillsWrote 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/the-ai-directory-company/agents-and-skills/integration-specification)<a href="https://agentmods.dev/skills/the-ai-directory-company/agents-and-skills/integration-specification"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/integration-specification/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/skills/the-ai-directory-company/agents-and-skills/integration-specification"><img src="https://agentmods.dev/badge/skills/the-ai-directory-company/agents-and-skills/integration-specification.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.00032 | $0.01462 |
| Opus 5.5 | $0.00013 | $0.00585 |
| Sonnet 5.5 | $0.00006 | $0.00292 |
| Haiku 4.5 | $0.00003 | $0.00146 |
Grade A, and why
integration-specification 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.
How it starts
The opening of the file, as written. The whole thing — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Specification
Before you start
Gather the following from the user. Do not proceed until you have answers to at least items 1-4:
- Which two systems are being connected? Name the source and destination. Include versions if relevant.
- What data flows between them? Entities, fields, direction (one-way or bidirectional), and expected volume.
- What triggers the data flow? Event-driven (webhook, message queue), scheduled (cron, polling), or on-demand (API call)?
- Authentication on both sides? API keys, OAuth, mutual TLS, service accounts — what does each system support?
- SLA requirements? Max acceptable latency, throughput targets, and uptime expectations.
- What happens when one system is down? Must data be queued, retried, or is loss acceptable?
If the user says "integrate system A with system B" without specifics, push back: "What data needs to move, in which direction, and what triggers the transfer?"
Integration specification template
1. Overview
Write 2-3 sentences covering:
- The two systems being connected and their roles (producer vs. consumer)
- The business purpose of the integration
- The integration pattern: synchronous request/response, asynchronous messaging, event-driven, or batch ETL
2. Data Flow Diagram
Define each data flow as a row:
| Flow | Source | Destination | Trigger | Payload | Frequency |
|---|---|---|---|---|---|
| Create order | Order Service | Fulfillment API | Order placed event | Order JSON | ~500/hour peak |
| Sync inventory | Warehouse DB | Product Service | Scheduled (every 5 min) | Inventory delta CSV | 288/day |
Include the direction arrow in the diagram. For bidirectional flows, document each direction as a separate row.
3. API Contracts
For each endpoint or message in the integration, specify:
- Method and URL (or queue/topic name for async)
- Request headers — Content-Type, Authorization, idempotency keys
- Request body — Full schema with field names, types, required/optional, and constraints
- Response body — Success shape and error shape
- Status codes — Every expected code with its meaning in this integration's context
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 132 lines · 32 tokens per session scan A 2dfa65232c4f
integration-specification is a skill published in the GitHub repository The-AI-Directory-Company/agents-and-skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 32 tokens to every session and 1,462 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
microservices-architecture
Microservices architecture patterns and best practices. Use when designing distributed systems, breaking down monoliths, or implementing service communication.
email-systems
Transactional email (Resend, SendGrid, SES), templates (React Email, MJML), deliverability (SPF/DKIM/DMARC), and inboxing best practices. Use when building email infrastructure, designing templates, or troubleshooting deliverability.
event-driven-architecture
Kafka, RabbitMQ, SQS/SNS, event sourcing, CQRS, saga patterns, dead letter queues, and idempotency. Use when designing asynchronous systems, implementing message-driven workflows, or building event streaming pipelines.
graphql-expert
GraphQL API design and implementation. Use when building GraphQL APIs, designing schemas, implementing resolvers, or optimizing GraphQL performance.
agent-go-expert
Specialist subagent: Go concurrency, error handling, stdlib patterns, Chi/Echo web frameworks specialist. Use when writing Go code, designing concurrent systems, or building Go web services. Trigger phrases: Go, Golang, goroutine, channel, Chi, Echo, stdlib, context, error handling, interface, module, go test.
agent-auth-specialist
Specialist subagent: OAuth 2.0/OIDC, JWT, session management, MFA, NextAuth/Clerk/Supabase Auth specialist. Use when implementing authentication, authorization, SSO, or security token management. Trigger phrases: login, auth, JWT, OAuth, session, password, MFA, 2FA, SSO, RBAC, permissions, roles.