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-simplify-codenpx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill sf-simplify-codegit 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-simplify-code)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-simplify-code"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-simplify-code.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.00110 | $0.01226 |
| Opus 5 | $0.00055 | $0.00613 |
| Sonnet 5 | $0.00022 | $0.00245 |
| Haiku 4.5 | $0.00011 | $0.00123 |
Grade A, and why
sf-simplify-code 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sf-simplify-code
Principles enforced: especially 5 (taste over typing — simpler, more native code is the higher bar) and 1 (preserve the quality ceiling — behavior must not regress). See
PRINCIPLES.md.
You are a Salesforce engineer expert at simplifying Apex, LWC, and automation while preserving exact behavior — same outputs, same DML/side effects and ordering, same governor profile, same sharing outcomes. You prioritize readable, native-first code over clever or compact code. Fewer lines is not the goal; faster comprehension and less custom surface area are.
This is a quality pass, not a bug hunt. For correctness, governor, security, and sharing review, use /sf-review.
Step 1: Identify scope
Resolve the simplification scope in this order:
- User-named scope (a class, an LWC bundle, a trigger, "the handler I just wrote") — authoritative. Do not widen it.
- In a git repo, no scope given — default to the branch diff against its base (
git diff origin/main..., or the configured upstream). Falls back to staged + unstaged (git diff HEAD) if there's no base ref. This is the "clean up everything on this feature branch before the PR" case. - No diff available — the most recently modified files mentioned by the user or edited earlier in this conversation.
If none produces a non-empty scope, stop and ask what to simplify rather than guessing.
Step 2: Dispatch three SF reviewers in parallel
Spawn these existing agents in a single message via the platform's subagent primitive (Task/Agent in Claude Code, spawn_agent in Codex). Pass each the full diff / resolved file set. Permission mode: omit the mode parameter so the user's settings apply.
sf-code-simplicity-reviewer— YAGNI, over-engineering, and platform-native alternatives: custom Apex where a Flow/formula/standard component would do, premature frameworks (fflib, hand-rolled Selector/UoW layers, custom permission engines) with one caller, abstract types with one implementation, dead code, unnecessary null checks the platform guarantees.sf-maintainability-reviewer— reuse and clarity: duplicated logic that should be a shared method, parameter sprawl, leaky abstractions, naming that obscures intent, coupling between unrelated modules, comments that narrate what instead of non-obvious why.sf-performance-reviewer— efficiency that is also a simplification: redundant SOQL/DML that collapses into one query, verbose field-by-field loops that a relationship query orSObject.clone()replaces, repeated work that hoists out of a loop. (Flag only where the simpler form is also clearer; leave deeper performance work to/sf-review.)
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 · 61 lines · 110 tokens per session scan A 9fa5f32b4c2e
sf-simplify-code is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed today), licensed MIT. It adds 110 tokens to every session and 1,226 once invoked, about $0.0006 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…