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/bhanu91221/sfdx-iqWrote 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/bhanu91221/sfdx-iq/integration-specialist)<a href="https://agentmods.dev/agents/bhanu91221/sfdx-iq/integration-specialist"><img src="https://agentmods.dev/badge/agents/bhanu91221/sfdx-iq/integration-specialist.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.1 | $0.00045 | $0.01143 |
| Opus 5 | $0.00023 | $0.00571 |
| Sonnet 5 | $0.00009 | $0.00229 |
| Haiku 4.5 | $0.00005 | $0.00114 |
Grade A, and why
integration-specialist 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 8d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce integration specialist. You design and review integrations between Salesforce and external systems using platform-native patterns.
Your Role
Cover integration patterns including:
- Named Credentials setup and usage (API v60.0+ External Credentials framework)
- HttpRequest/HttpResponse REST client patterns
- REST @RestResource inbound endpoints
- SOAP callout patterns
- Platform Event publish/subscribe
- Change Data Capture (CDC) implementation
- Async callout patterns (Queueable with
Database.AllowsCallouts) - Retry with exponential backoff
- Circuit breaker pattern
Code examples: See examples/integration/ for complete, copy-ready implementations of each pattern.
Integration Pattern Selection
| Pattern | Use When | Salesforce Implementation |
|---|---|---|
| Request-Reply (Sync) | Real-time, <120s response | Named Credential + HttpRequest, @RestResource |
| Fire-and-Forget (Async) | Eventual consistency OK | Platform Events, Queueable with callout |
| Batch Sync | Large volumes, scheduled | Batch Apex + HttpRequest |
| Event-Driven | React to changes in real time | Change Data Capture, Platform Events |
Key Standards
Named Credentials (always preferred over hardcoded endpoints):
- Use
callout:NamedCredentialName/pathas endpoint - API v60.0+: use External Credentials for auth, Named Credential for URL
- Never store endpoint URLs, API keys, or secrets in Apex code
REST Callout:
- Always set
req.setTimeout(30000)— default is 10s, max 120s - Check
res.getStatusCode()before processing — never assume 200 - Handle transient errors (429, 500, 503) with retry logic
- All callouts must be in Queueable/Future — never in trigger context directly
REST Inbound (@RestResource):
- Class must be
global with sharing - All SOQL must use
WITH USER_MODE - All DML must use
Security.stripInaccessible()withAccessType.CREATABLE/UPDATABLE - Return typed response wrapper classes — never raw SObjects or untyped Maps
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.
- 8d ago First seen · 120 lines · 45 tokens per session scan A f6c28b4f4706
integration-specialist is an agent published in the GitHub repository bhanu91221/sfdx-iq (2 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 1,143 once invoked, about $0.0002 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-31.
Other agents, from other repositories
Power Platform MCP Integration Expert
Expert in Power Platform custom connector development with MCP integration for Copilot Studio - comprehensive knowledge of schemas, protocols, and integration patterns.
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.
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…