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 skills add rsts-dev/claude-buddy-marketplace --skill salesforcesetupgit clone --depth 1 https://github.com/rsts-dev/claude-buddy-marketplaceWrote 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/rsts-dev/claude-buddy-marketplace/salesforcesetup)<a href="https://agentmods.dev/skills/rsts-dev/claude-buddy-marketplace/salesforcesetup"><img src="https://agentmods.dev/badge/skills/rsts-dev/claude-buddy-marketplace/salesforcesetup/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/rsts-dev/claude-buddy-marketplace/salesforcesetup"><img src="https://agentmods.dev/badge/skills/rsts-dev/claude-buddy-marketplace/salesforcesetup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 28 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 41 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 55 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00100 | $0.00654 |
| Opus 5 | $0.00050 | $0.00327 |
| Sonnet 5 | $0.00020 | $0.00131 |
| Haiku 4.5 | $0.00010 | $0.00065 |
Grade A, and why
SalesforceSetup 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 12d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SalesforceSetup
Install Salesforce's official agent-skills collection by driving the upstream install, the same thin-wrapper way /setup:lifeos drives the LifeOS installer. Nothing is vendored — the skill fetches the upstream repo's current install instructions at run time and drives them with permission.
What gets installed
The salesforce-development plugin from forcedotcom/sf-skills (a marketplace named salesforce, ~41 skills), including:
- agentforce-generate / -observe / -test — build, monitor, and security-test Agentforce agents
- dx-code-analyzer-run / -configure / -custom-rule-create — code analysis
- dx-org-manage — scratch-org / org lifecycle
- automation-flow-generate — Flow automation
These complement the buddy salesforce domain.
Customization
Before executing, check ~/.claude/LIFEOS/USER/CUSTOMIZATIONS/SKILLS/SalesforceSetup/PREFERENCES.md. If present, load and apply it; otherwise use defaults.
Prerequisites
- Salesforce CLI (
sf) — required by most skills - Node.js + npm — for
npx skills add/ CLI tooling
If a prerequisite is missing, report it and let the user decide whether to proceed.
Workflow Routing
| Workflow | Trigger | File |
|---|---|---|
| InstallSalesforceSkills | Any /setup:salesforce invocation |
Workflows/InstallSalesforceSkills.md |
Hard rules
- Thin wrapper. Fetch the upstream install at run time; do not vendor the skills. Upstream warns skills may be renamed/removed between releases.
- Permission before mutation.
/plugin marketplace add/npx skills addrun only after the user confirms. - Additive. Never remove existing skills or marketplaces.
Source
- Repo:
https://github.com/forcedotcom/sf-skills(marketplacesalesforce, pluginsalesforce-development) - Read the upstream README at run time for the current install command.
Examples
User: "/setup:salesforce"
→ Checks Salesforce CLI (`sf`) + Node
→ Fetches the sf-skills README for the current install command
→ Drives `/plugin marketplace add forcedotcom/sf-skills` (+ install salesforce-development) or `npx skills add forcedotcom/sf-skills`, with permission
→ Verifies the skills are available; reports
What ships with it
1 file 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.
- 12d ago First seen · 58 lines · 0 tokens per session scan A f162fa6a31a2
SalesforceSetup is a skill published in the GitHub repository rsts-dev/claude-buddy-marketplace (17 stars, last pushed 21d ago), licensed MIT. It adds 100 tokens to every session and 654 once invoked, about $0.0005 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
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…