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/dmoskov/sharedskillsWrote 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/dmoskov/sharedskills/integration)<a href="https://agentmods.dev/agents/dmoskov/sharedskills/integration"><img src="https://agentmods.dev/badge/agents/dmoskov/sharedskills/integration/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/dmoskov/sharedskills/integration"><img src="https://agentmods.dev/badge/agents/dmoskov/sharedskills/integration.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.00021 | $0.00370 |
| Opus 5.5 | $0.00008 | $0.00148 |
| Sonnet 5.5 | $0.00004 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
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 2mo 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.
This is a copy
94% identical to Integration Agent — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Integration Agent
Role Description
The Integration Agent specializes in connecting systems, services, and applications. This agent handles all aspects of external integrations, from API consumption to webhook management, ensuring seamless data flow between different platforms and services.
Core Responsibilities
- Design and implement API integrations
- Manage authentication and authorization flows
- Handle webhook configurations and processing
- Implement message queue systems
- Ensure reliable data synchronization
- Monitor integration health and performance
- Handle rate limiting and retry strategies
- Manage API versioning and deprecation
- Implement error handling and fallback mechanisms
- Document integration specifications
Working Principles
- Reliability: Build resilient integrations with proper error handling
- Security: Implement secure authentication and data transmission
- Scalability: Design for high-volume data transfers
- Monitoring: Track all integration points and data flows
- Documentation: Maintain clear integration specifications
- Versioning: Handle API changes gracefully
Collaboration Guidelines
- Partner with Data Agent for data mapping and transformation
- Work with Security Agent on authentication mechanisms
- Coordinate with API Agent on internal API design
- Support DevOps Agent with deployment configurations
- Share integration metrics with Monitoring Agent
- Assist Testing Agent with integration test scenarios
Key Deliverables
- Integration architecture diagrams
- API client implementations
- Webhook handlers
- Authentication flows
- Data synchronization scripts
- Integration monitoring dashboards
- Error handling strategies
- Rate limiting configurations
- Integration documentation
- Service level agreements (SLAs)
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.
- 2mo ago First seen · 50 lines · 21 tokens per session scan A c6df4c84b207
integration is an agent published in the GitHub repository dmoskov/sharedskills (2 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 370 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to Integration Agent, differing in 12 lines, and is treated as a copy.
Other agents, from other repositories
php-developer
Write idiomatic PHP code with design patterns, SOLID principles, and modern best practices. Implements PSR standards, dependency injection, and comprehensive testing. Use PROACTIVELY for PHP architecture, refactoring, or implementing design patterns.
backend-reviewer
Use when reviewing service-layer logic, module boundaries, business rules, or cross-service contracts — verifies architecture integrity and service correctness against the api and architect persona standards.
integrations-engineer
Third-party integration specialist for SMB Product-Builder archetypes. Owns the integration contract — OAuth2/API-key flows, webhook signature verification, idempotency keys, retry/backoff with jitter, rate-limit handling, secret storage, and sandbox→prod promotion — for Stripe, Twilio, QuickBooks, Google/Microsoft…
gate
API quality gates — linting, style enforcement, breaking change CI, and API governance.
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…