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/divingsbysangam/salesforce-compound-engineering-plugin/sf-setupnpx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill sf-setupgit clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-pluginWrote 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/divingsbysangam/salesforce-compound-engineering-plugin/sf-setup)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-setup"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-setup.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.00104 | $0.00699 |
| Opus 5 | $0.00052 | $0.00349 |
| Sonnet 5 | $0.00021 | $0.00140 |
| Haiku 4.5 | $0.00010 | $0.00070 |
Grade A, and why
sf-setup 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 yesterday.
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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sf-setup
Verify prerequisites, surface missing pieces, and walk the user through installing or configuring each one.
<feature_description> #$ARGUMENTS </feature_description>
Salesforce Angle
- Check
sf --version(Salesforce CLI v2+) and report install command if missing. - Check for
sfdx-project.jsonin the project root (current dir or first ancestor with one). - Check
.mcp.jsonfor Context7 and@salesforce/mcpentries; offer to add the Salesforce DX MCP server. - Verify Claude Code plugin install:
claude /plugin listincludessf-compound-engineering. - Optional: check
ast-grepCLI presence (used by review agents for structural Apex/LWC analysis).
Interaction Method
When asking the user a question, use the platform's blocking question tool (AskUserQuestion in Claude Code, request_user_input in Codex, ask_user in Gemini). Fall back to numbered options in chat when no blocking tool is available. Ask one question at a time. Prefer concise single-select choices when natural options exist.
Procedure
- Read the
<feature_description>block and any referenced files. - Run the fail-closed checks below. Do not report a check as passing because it was skipped.
- If a command errors, times out, or is missing, record
<check>=unavailable: <reason>and tell the user how to install or fix it. - Ask with the blocking question tool when a choice affects scope or risk.
Fail-closed checks
| Check | Preferred | Fallback | Report |
|---|---|---|---|
| CLI | sf --version |
which sf |
version string or cli=unavailable |
| Project | read sfdx-project.json walking ancestors |
none | path or project=unavailable: no sfdx-project.json |
| MCP | read .mcp.json |
none | servers listed or mcp=unavailable |
| Plugin | claude /plugin list |
none | plugin present or plugin=unavailable |
Cross-skill integration
| Need | Delegate to | Reason |
|---|---|---|
| Deploy / retrieve / test / org CLI | sf-cli |
This skill only verifies install |
| Generate Apex / Flow / metadata | matching *-generate skill |
Authoring is not setup |
| Agentforce authoring | agentforce-develop |
Different toolchain |
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.
- yesterday First seen · 55 lines · 104 tokens per session scan A f834c4275ae7
sf-setup is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed today), licensed MIT. It adds 104 tokens to every session and 699 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-09-03.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…