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-clinpx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill sf-cligit 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-cli)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-cli"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-cli.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.00136 | $0.01221 |
| Opus 5 | $0.00068 | $0.00611 |
| Sonnet 5 | $0.00027 | $0.00244 |
| Haiku 4.5 | $0.00014 | $0.00122 |
Grade A, and why
sf-cli 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 4d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Salesforce CLI Skill
Reference for common sf CLI commands used in Salesforce development workflows. This skill does not generate metadata — it runs CLI against metadata that already exists.
Cross-skill integration
| Need | Delegate to | Reason |
|---|---|---|
| New Apex / tests | apex-generate |
Author before deploy |
| New Flow XML | flow-generate |
Pipeline before deploy |
| New object / field / tab / app | metadata-generate |
Schema before deploy |
| New FlexiPage / LEX app | lightning-page-generate |
Page orchestration |
| New permission set | permission-set-generate |
Least privilege |
| CLI / project / MCP missing | sf-setup |
Prerequisites |
| Agentforce publish | agentforce-develop |
Agent CLI, not sf project deploy |
Fail-closed deploy
Every deploy-shaped request follows this contract. Do not report a deploy as successful because a command was skipped.
- Preferred — validate:
sf project deploy start --dry-run --jsonwith an explicit--source-dir,--metadata, or--manifest. Paste the JSON (or a tight error extract) on the Compile line. - Fallback if dry-run is unrecognized:
sf project deploy validate --jsonwith the same scope. - If both fail to run (CLI missing, not logged in, timeout, empty/uncertain output):
compile=unavailable: <reason>. That is not a pass. - Production: do not run a non-dry-run deploy to a production org without explicit user confirmation of the org alias. Prefer validate-then-quick-deploy when the org supports it.
- Destructive / delete: confirm with the user before
sf project deleteor a destructive manifest. - Always pass
--jsonwhen parsing results. Always name--target-orgwhen the default org is not the intended target.
Deploy
# Deploy source to org
sf project deploy start --source-dir force-app
# Deploy specific metadata
sf project deploy start --metadata ApexClass:MyClass
# Validate without deploying (dry run)
sf project deploy start --dry-run --source-dir force-app
# Deploy with test execution
sf project deploy start --source-dir force-app --test-level RunLocalTests
# Check deploy status
sf project deploy report
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.
- 4d ago First seen · 166 lines · 136 tokens per session scan A 119c61f95b47
sf-cli is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed today), licensed MIT. It adds 136 tokens to every session and 1,221 once invoked, about $0.0007 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-31.
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…