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 divingsbysangam/salesforce-compound-engineering-plugin/plugin install sf-compound-engineeringWrote 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-work)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-work"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-work.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.1 | $0.00100 | $0.01004 |
| Opus 5 | $0.00050 | $0.00502 |
| Sonnet 5 | $0.00020 | $0.00201 |
| Haiku 4.5 | $0.00010 | $0.00100 |
Grade A, and why
sf-work 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 2d 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 — 64 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sf-work
Persona dispatch. This skill dispatches personas as isolated subagents — see the
dispatching-parallel-personasskill for the mechanics (isolated subagents, same-response parallelism, same-file-conflict check). Review personas are referenced from../sf-review/references/personas/, research personas from../sf-plan/references/personas/.
Principles enforced: 1 (preserve the quality ceiling), 2 (verifiability), 3 (jagged intelligence). See
PRINCIPLES.md.
Required reads
Procedure lives in sibling files, not only in this orchestrator:
- Step 0: Pre-Implementation Research (parallel) — read
references/step-0-pre-implementation-research-parallel.mdbefore acting on this section. - Step 1: Route via Indexes — read
references/step-1-route-via-indexes.mdbefore acting on this section. - Step 2: Internal-First Implementation — read
references/step-2-internal-first-implementation.mdbefore acting on this section. - Step 2.5: Test-First (Red → Green → Refactor) — read
references/step-2-5-test-first-red-green-refactor.mdbefore acting on this section. - Step 3: Implementation Standards — read
references/step-3-implementation-standards.mdbefore acting on this section. - Step 4: System-Wide Test Check — read
references/step-4-system-wide-test-check.mdbefore acting on this section. - Step 5: Incremental Commits — read
references/step-5-incremental-commits.mdbefore acting on this section. - Output — read
references/output.mdbefore acting on this section. - After Implementation — read
references/after-implementation.mdbefore acting on this section.
Copy-paste-to-agent
Implement a Salesforce feature against an existing plan. Before writing code, dispatch
sf-learnings-researcher and sf-repo-research-analyst in parallel. Then write code AND tests
together — verification is not a follow-up. Before declaring complete, answer all five
System-Wide Test Check questions: trigger contexts, bulk at 200+, governor limits, sharing,
integration mocks. If the plan has a Verification Strategy section, the implementation must
satisfy every field; do not relax it.
What ships with it
9 files 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.
- references/after-implementation.md 483 B
- references/output.md 169 B
- references/step-0-pre-implementation-research-parallel.md 450 B
- references/step-1-route-via-indexes.md 913 B
- references/step-2-5-test-first-red-green-refactor.md 1.3 KB
- references/step-2-internal-first-implementation.md 420 B
- references/step-3-implementation-standards.md 954 B
- references/step-4-system-wide-test-check.md 2.8 KB
- references/step-5-incremental-commits.md 289 B
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.
- 2d ago First seen · 64 lines · 100 tokens per session scan A 31b540d82b11
sf-work is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 2d ago), licensed MIT. It adds 100 tokens to every session and 1,004 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.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…