forcedotcom/sf-skills is a collection of reusable instructions that help AI coding agents build and work with Salesforce applications and platform features. Developers use it for Agentforce agents, Lightning apps, Flow, Apex, SOQL, Lightning Web Components, and related Salesforce configuration. The catalogue entries are the repository’s skills, plugins, commands, MCP servers, and agents for AI tools that support skills.
Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add forcedotcom/sf-skills/plugin install salesforce-developmentWrote 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/commands/forcedotcom/sf-skills/plugin-recommendations)<a href="https://agentmods.dev/commands/forcedotcom/sf-skills/plugin-recommendations"><img src="https://agentmods.dev/badge/commands/forcedotcom/sf-skills/plugin-recommendations/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/commands/forcedotcom/sf-skills/plugin-recommendations"><img src="https://agentmods.dev/badge/commands/forcedotcom/sf-skills/plugin-recommendations.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.00020 | $0.00439 |
| Opus 5.5 | $0.00008 | $0.00176 |
| Sonnet 5.5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
plugin-recommendations 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 1mo 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.
What it actually says
Manage this plugin's uninstalled-plugin recommendation sensitivity — how readily it proposes an uninstalled Salesforce plugin that matches your task. Default is standard; off is a true hard-off (no recommendation on any surface: SessionStart, prompt submission, the bypass gate, or the discovery command) and honors SF_DISABLE_PLUGIN_MATCH.
Named levels, from least to most readily triggered: off, low (threshold 6.0), standard (threshold 3.5, default), high (threshold 3.0). high sensitivity needs the least evidence before proposing a plugin, low needs the most — same relationship as a smoke detector's sensitivity dial.
A custom number from 1.0 to 10.0 is also accepted for finer control, on that same threshold scale: it is compared directly against the match score, so a lower number triggers more readily (more sensitive) and a higher number triggers less readily (less sensitive, more evidence required). It is easy to get this backwards — "high" sensitivity is the low end of the number range (3.0), not the high end.
If the user asked to turn it off:
${CLAUDE_PLUGIN_ROOT}/scripts/sf-context plugin-match-config off
If the user asked to turn it on (reset to the plugin's default):
${CLAUDE_PLUGIN_ROOT}/scripts/sf-context plugin-match-config on
If the user asked to set a level or custom number (e.g. low, high, or 7.5):
${CLAUDE_PLUGIN_ROOT}/scripts/sf-context plugin-match-config set <value>
Otherwise show current status:
${CLAUDE_PLUGIN_ROOT}/scripts/sf-context plugin-match-config status
Output the result verbatim to the user.
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.
- 1mo ago First seen · 38 lines · 20 tokens per session scan A 5c2a5749f80e
plugin-recommendations is a command published in the GitHub repository forcedotcom/sf-skills (1,104 stars, last pushed yesterday), licensed Apache-2.0. It adds 20 tokens to every session and 439 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
add-note
Add an internal or external note to a ConnectWise PSA ticket.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.