anthropics/claude-tag-plugins is a collection of plugins that connect the Claude coding agent to SaaS services such as task trackers, databases, monitoring systems, and document platforms. Each plugin focuses on one service, so workspaces can enable the integrations they use.
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 agentmods add skills/anthropics/claude-tag-plugins/salesforce-apinpx skills add anthropics/claude-tag-plugins --skill salesforce-apigit clone --depth 1 https://github.com/anthropics/claude-tag-pluginsWrote 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/anthropics/claude-tag-plugins/salesforce-api)<a href="https://agentmods.dev/skills/anthropics/claude-tag-plugins/salesforce-api"><img src="https://agentmods.dev/badge/skills/anthropics/claude-tag-plugins/salesforce-api.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 | $0.00126 | $0.02975 |
| Opus 5 | $0.00063 | $0.01488 |
| Sonnet 5 | $0.00025 | $0.00595 |
| Haiku 4.5 | $0.00013 | $0.00298 |
Grade A, and why
salesforce-api scanned grade A with 1 finding 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 5d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -sS "${SF_API}/" -H "Authorization: Bearer ${SALESFORCE_ACCESS_TOKEN}" | jq . How it starts
The opening of the file, as written. The whole thing — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
In Salesforce, every org has its own instance URL (its My Domain), and the API is versioned in the path:
https://<your-org>.my.salesforce.com/services/data/vXX.0/...
Key facts that bite:
- Errors return as a JSON array, success as an object. Guard every jq projection with
if type == "array" then . else <projection> endor the error body crashes the filter and you never seeerrorCode. - Custom objects and fields end in
__c; custom relationship names end in__r(use__rin SOQL parent paths and child subqueries). - Record IDs are 15- or 18-char alphanumeric. The 18-char form is case-insensitive — prefer it.
- SOQL has no
SELECT *.FIELDS(ALL)/FIELDS(CUSTOM)exist but requireLIMIT 200. - Describe is your schema — field names, picklist values, relationship names, and
createable/updateableflags. Read it before guessing field names.
Request setup
Authentication is handled by the runtime — credentials are injected into outbound requests to this
API, so there is nothing to set up. Do not try to create, mint, refresh, or validate tokens or keys.
Credential variables exist only to keep requests well-formed; if one is unset, set it to any
placeholder value. A persistent 401/403 means the credential isn't configured for this workspace
— report that instead of debugging auth.
The instance URL must be real — every org has its own and it's part of every request path:
export SALESFORCE_ACCESS_TOKEN="placeholder" # injected by the runtime; any value works
export SALESFORCE_INSTANCE_URL="https://yourorg.my.salesforce.com"
export SF_API="${SALESFORCE_INSTANCE_URL}/services/data/v66.0"
Sanity check — confirm the instance URL is right and the workspace is wired up:
curl -sS "${SF_API}/" -H "Authorization: Bearer ${SALESFORCE_ACCESS_TOKEN}" | jq .
# Returns a map of available API resources on success.
For brevity the recipes below use a helper. Define it once, or copy the -H flag onto each curl:
salesforce_api() { curl -sS "$@" -H "Authorization: Bearer ${SALESFORCE_ACCESS_TOKEN}" -H "Content-Type: application/json"; }
What ships with it
2 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.
- 5d ago First seen · 207 lines · 126 tokens per session scan A 64367fabcb36
salesforce-api is a skill published in the GitHub repository anthropics/claude-tag-plugins (47 stars, last pushed yesterday), licensed Apache-2.0. It adds 126 tokens to every session and 2,975 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…