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/skills/forcedotcom/sf-skills/platform-lsp-integrate)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/platform-lsp-integrate"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/platform-lsp-integrate/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/forcedotcom/sf-skills/platform-lsp-integrate"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/platform-lsp-integrate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
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.00207 | $0.03405 |
| Opus 5 | $0.00103 | $0.01702 |
| Sonnet 5 | $0.00041 | $0.00681 |
| Haiku 4.5 | $0.00021 | $0.00341 |
Grade A, and why
platform-lsp-integrate 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 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.
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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using the Salesforce LSP
The salesforce-development plugin hosts a local MCP server named
salesforce-lsp that lazily spawns Salesforce Language Server children and
exposes their semantic capabilities as MCP tools. This skill is the contract
other skills follow when they call those tools, and the answer to "how do I use
the Salesforce LSP?" — what each tool does, how to read its result, what every
error code means, and how to fall back when the host is absent.
This is a documentation/reference skill. It does not author or deploy code; it tells you (and other skills) how to drive the LSP tools correctly.
This plugin build vendors Apex + SOQL only. The
salesforce-lsphost ships the Apex language server (@salesforce/apex-ls) and the SOQL language server. The LWC language server is intentionally not bundled in this plugin — thelwc.*tools are registered by the host but will always return anunavailable-class envelope here. Treat anylwc.*call as unavailable and use the fallback (read the component source / deploy-compile).
When to Use This Skill
- A user asks how to use the Salesforce LSP, or which LSP/MCP tools are available.
- A user asks what a specific tool does (
apex.diagnostics,validate_soql,complete_soql, etc.) or how to read its output. - An LSP tool returned an error envelope (
lsp_disabled,spawn_timeout,circuit_open,no_apex_workspace,no_org_connected) and you need to know what it means and how to recover. - You're authoring or reviewing another skill that calls an LSP tool and need the canonical call/fallback pattern.
- The LSP seems broken and you need to debug it (
lsp.health,${CLAUDE_PLUGIN_ROOT}/bin/lsp-doctor, the kill switch).
The Tools
All tools are served by the MCP server salesforce-lsp (invoke names follow
the plugin-prefixed pattern:
mcp__plugin_salesforce-development_salesforce-lsp__<tool_name>, where dots in
tool names become underscores — e.g. apex.diagnostics becomes
mcp__plugin_salesforce-development_salesforce-lsp__apex_diagnostics). Spawning
is lazy: a tool that needs a language server brings the child up on first call (a
one-time cold start of a few seconds for Apex), then reuses it. The pure
static-analysis tools never spawn anything.
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 · 231 lines · 207 tokens per session scan A 633cec0b7fee
platform-lsp-integrate is a skill published in the GitHub repository forcedotcom/sf-skills (974 stars, last pushed today), licensed Apache-2.0. It adds 207 tokens to every session and 3,405 once invoked, about $0.0010 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-09-03.
Other skills, from other repositories
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…