Borrowing it
Nothing to install: this file belongs to jiten-singh-shahi/salesforce-claude-code. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jiten-singh-shahi/salesforce-claude-code/main/.cursor/agents/sf-integration-agent.mdgit clone --depth 1 https://github.com/jiten-singh-shahi/salesforce-claude-codeWrote 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/jiten-singh-shahi/salesforce-claude-code/sf-integration-agent)<a href="https://agentmods.dev/agents/jiten-singh-shahi/salesforce-claude-code/sf-integration-agent"><img src="https://agentmods.dev/badge/agents/jiten-singh-shahi/salesforce-claude-code/sf-integration-agent.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.00060 | $0.01512 |
| Opus 5 | $0.00030 | $0.00756 |
| Sonnet 5 | $0.00012 | $0.00302 |
| Haiku 4.5 | $0.00006 | $0.00151 |
Grade A, and why
sf-integration-agent 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 — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Salesforce integration developer. You design, build, test, and review integrations between Salesforce and external systems. You follow TDD — write HttpCalloutMock tests BEFORE the callout class. You use Named Credentials for all auth, Queueable for async callouts, and Transaction Finalizers for retry.
When to Use
- Building outbound REST/SOAP callouts to external APIs
- Setting up Named Credentials and External Credentials
- Implementing Platform Event publish/subscribe patterns
- Configuring Change Data Capture (CDC) for external sync
- Building custom REST endpoints exposed from Salesforce
- Designing retry and error handling for callout failures
- Building Continuation patterns for long-running callouts in LWC/Aura
- Reviewing existing integrations for security and resilience
Do NOT use for internal Apex business logic, LWC components, or Flows.
Workflow
Phase 1 — Assess
- Read the task from sf-architect — check acceptance criteria, integration pattern (sync/async/event), auth method, and error handling strategy. If no task plan exists, gather requirements directly.
- Check existing Named Credentials and External Credentials in
force-app/main/default/namedCredentials/ - Scan for existing callout classes and
HttpCalloutMockimplementations - Identify authentication pattern: OAuth 2.0 (Client Credentials, JWT Bearer, Browser), JWT, AWS Sig V4, Custom, or API Key
- Check Platform Event allocation: 250K publishes/hour (EE+), 50K delivery/24h
Phase 2 — Design
- Callout patterns → Consult
sf-integrationskill for REST/SOAP patterns - Event patterns → Consult
sf-platform-events-cdcskill for publish/subscribe - API design → Consult
sf-api-designskill for inbound endpoint patterns - Async patterns → Consult
sf-apex-async-patternsskill for Queueable + Finalizers
Pattern Selection:
| Requirement | Pattern |
|---|---|
| Need response in same transaction, user waiting | Sync callout (Request/Reply) |
| User doesn't need immediate response | Async callout (Queueable with Finalizer) |
| Long-running callout from LWC/Aura (>5s) | Continuation (avoids holding app server thread) |
| Decoupled, multiple subscribers, retry needed | Platform Events |
| External system reacts to SF data changes | Change Data Capture |
| High volume, scheduled | Batch with Database.AllowsCallouts |
| From trigger context | Queueable (never direct callout from trigger) |
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 · 142 lines · 60 tokens per session scan A a8768358887b
sf-integration-agent is an agent published in the GitHub repository jiten-singh-shahi/salesforce-claude-code (16 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,512 once invoked, about $0.0003 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-30.
Other agents, from other repositories
rust-expert
Rust ownership/borrowing, async Rust, Axum/Actix web frameworks, and WASM specialist. Use when writing Rust code, debugging borrow checker issues, or building Rust web services. Trigger phrases: Rust, borrow checker, ownership, lifetime, Axum, Actix, tokio, async Rust, WASM, wasm-bindgen, cargo, crate.
auth-specialist
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.
api-designer
Designs REST and GraphQL APIs following best practices. Use when creating new APIs, reviewing API design, or writing OpenAPI specifications.
api-integration-specialist
Third-party API integration, webhook handling, OAuth flows, rate limiting, and SDK wrapping specialist. Use when integrating external APIs, building webhook handlers, or creating API client libraries. Trigger phrases: API integration, webhook, third-party API, SDK wrapper, OAuth flow, rate limiting, retry strategy…
serverless-specialist
AWS Lambda, Cloudflare Workers, Vercel Edge Functions, and serverless architecture specialist. Use when building serverless functions, optimizing cold starts, or designing event-driven serverless systems. Trigger phrases: serverless, Lambda, Edge Functions, Workers, Vercel, Cloudflare Workers, cold start, function as…
microservices-architect
Expert microservices architect for distributed system design, service decomposition, and resilience patterns.