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/skills/sf-integration/SKILL.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/skills/jiten-singh-shahi/salesforce-claude-code/sf-integration)<a href="https://agentmods.dev/skills/jiten-singh-shahi/salesforce-claude-code/sf-integration"><img src="https://agentmods.dev/badge/skills/jiten-singh-shahi/salesforce-claude-code/sf-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/skills/jiten-singh-shahi/salesforce-claude-code/sf-integration"><img src="https://agentmods.dev/badge/skills/jiten-singh-shahi/salesforce-claude-code/sf-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.00038 | $0.03286 |
| Opus 5 | $0.00019 | $0.01643 |
| Sonnet 5 | $0.00008 | $0.00657 |
| Haiku 4.5 | $0.00004 | $0.00329 |
Grade A, and why
sf-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 9d 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 — 480 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce Integration Patterns
Procedures for building integrations between Salesforce and external systems. Limits, auth protocols, and pattern decision matrices live in the reference file.
@../_reference/INTEGRATION_PATTERNS.md
When to Use
- Designing a new integration between Salesforce and an external system
- Choosing between REST callout, SOAP callout, Bulk API, or Composite API
- Implementing an inbound REST API endpoint in Salesforce
- Configuring Named Credentials and External Credentials for authentication
- Adding retry logic to callout classes for resilience
- Migrating from Connected Apps to External Client Apps (Spring '26+)
Outbound REST Callout — Complete Pattern
public with sharing class OrderManagementIntegration {
private static final String NAMED_CREDENTIAL = 'OrderManagementAPI';
private static final Integer TIMEOUT_MS = 10000;
private static final Integer MAX_RETRIES = 2;
public static OrderResponse createExternalOrder(OrderRequest orderData) {
HttpRequest req = new HttpRequest();
req.setEndpoint('callout:' + NAMED_CREDENTIAL + '/api/v2/orders');
req.setMethod('POST');
req.setHeader('Content-Type', 'application/json');
req.setHeader('Accept', 'application/json');
req.setTimeout(TIMEOUT_MS);
req.setBody(JSON.serialize(orderData));
return executeWithRetry(req, MAX_RETRIES);
}
public static OrderResponse getOrderStatus(String externalOrderId) {
HttpRequest req = new HttpRequest();
req.setEndpoint('callout:' + NAMED_CREDENTIAL +
'/api/v2/orders/' + EncodingUtil.urlEncode(externalOrderId, 'UTF-8'));
req.setMethod('GET');
req.setHeader('Accept', 'application/json');
req.setTimeout(TIMEOUT_MS);
return executeWithRetry(req, MAX_RETRIES);
}
/**
* In-transaction retry for transient network glitches.
* For true backoff, use Queueable chaining with
* AsyncOptions.minimumQueueableDelayInMinutes between attempts.
*/
private static OrderResponse executeWithRetry(HttpRequest req, Integer retries) {
Http http = new Http();
HttpResponse res;
Exception lastException;
for (Integer attempt = 0; attempt <= retries; attempt++) {
try {
res = http.send(req);
if (res.getStatusCode() == 200 || res.getStatusCode() == 201) {
return (OrderResponse) JSON.deserialize(
res.getBody(), OrderResponse.class);
}
if (res.getStatusCode() == 429) {
if (attempt == retries) {
throw new IntegrationException(
'Rate limited (429) after ' + (retries + 1) + ' attempts.');
}
continue;
}
if (res.getStatusCode() >= 500 && attempt < retries) continue;
throw new IntegrationException(
'HTTP ' + res.getStatusCode() + ': ' + res.getBody());
} catch (System.CalloutException e) {
lastException = e;
if (attempt == retries) {
throw new IntegrationException(
'Callout failed after ' + (retries + 1) +
' attempts: ' + e.getMessage(), e);
}
}
}
throw new IntegrationException('Unexpected retry loop exit');
}
public class OrderRequest {
public String externalAccountId;
public String productCode;
public Integer quantity;
public Decimal unitPrice;
public String currency_x;
}
public class OrderResponse {
public String orderId;
public String status;
public String message;
public String createdAt;
}
public class IntegrationException extends Exception {}
}
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.
- 9d ago First seen · 480 lines · 38 tokens per session scan A 6ebc0974e26e
sf-integration is a skill published in the GitHub repository jiten-singh-shahi/salesforce-claude-code (16 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 3,286 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-30.
Other skills, from other repositories
case-feed-send-email-action
Use when configuring the outbound Send Email quick action in Lightning Case Feed — creating the action in Setup on Case (Action Type = Send Email), attaching a default Custom email template, setting predefined To/CC/BCC values, wiring QuickAction.QuickActionDefaultsHandler Apex defaults, respecting the Lightning…
approval-process-apex-patterns
Programmatically driving Salesforce Approval Processes from Apex — Approval.process(ProcessSubmitRequest) to submit, ProcessWorkitemRequest to approve / reject / reassign, recall semantics, querying ProcessInstance and ProcessInstanceWorkitem to find pending approvals, and the bulk-submit / bulk-action error-row…
connected-app-troubleshooting
Troubleshooting Connected App OAuth flows — IP relaxation vs IP restriction, refresh token policy traps (default kills the connection on first refresh), session-revocation semantics, the OAuth error-code catalog (invalidgrant, invalidclientid, unsupportedgranttype), per-user vs admin-pre-approved flows, and the…
connected-apps-and-auth
Use when designing, reviewing, or troubleshooting Salesforce connected apps, External Client Apps, Named Credentials, External Credentials, and OAuth-based integration access. Triggers: 'connected app', 'OAuth flow', 'client credentials', 'JWT bearer', 'Named Credential', 'External Credential', 'integration user', 'IP…
api-contract-documentation
Produce or review API contract documentation for Salesforce integrations: versioning policy artifacts, request/response schema specs, error code catalogs, rate limit documentation, OpenAPI generation for sObjects. Trigger keywords: Salesforce API versioning policy, API end-of-life policy, document API endpoints, REST…
activity-and-task-patterns
Task and Event objects: polymorphic WhatId/WhoId, Activity object model, ActivityHistory vs OpenActivity, activity timeline customization, bulk task creation, Einstein Activity Capture boundaries. NOT for turning on EAC or calendar sync — use admin/einstein-activity-capture-setup. NOT for Email-to-Case — use…