Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-pluginnpx agentmods add skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-polishWrote 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-polish)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-polish"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-polish/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/divingsbysangam/salesforce-compound-engineering-plugin/sf-polish"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-polish.svg" alt="Reviewed on agentmods" width="80" 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.00126 | $0.01521 |
| Opus 5 | $0.00063 | $0.00760 |
| Sonnet 5 | $0.00025 | $0.00304 |
| Haiku 4.5 | $0.00013 | $0.00152 |
Grade A, and why
sf-polish 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 9d 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 — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sf-polish
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). The reviewers it dispatches (e.g.sf-lwc-accessibility-guardian,sf-aura-migration-advisor) are review personas referenced from../sf-review/references/personas/.
Principles enforced: especially 1 (preserve the quality ceiling — the finished thing must feel right, not merely compile) and 5 (taste over typing — UX and copy are human-judgment calls). See
PRINCIPLES.md.
This is the back "bread" of the compound loop. Correctness has passed /sf-review; now refine the experience: visual design, layout, accessibility, motion, and copy. It is stack-aware — it detects the front-end surface in scope and applies the right lens through a profile registry, so new Salesforce front-end stacks are added as profiles rather than rewrites.
Polish is a quality/taste pass, not a bug or governor hunt — that is /sf-review. Polish does not change Apex business logic.
Step 1: Resolve scope and detect the surface
Resolve scope: a user-named component/app, else the branch diff (git diff origin/main..., falling back to git diff HEAD), else recently edited files.
Classify the changed files into front-end surfaces:
-
*.js/*.html/*.cssinside anlwc/bundle → LWC -
*.cmp/*.app/*Controller.js/*Helper.jsinsideaura/→ Aura -
LWR / Experience Cloud bundles (
experiences/,digitalExperiences/, themes/branding sets) → Experience Cloud (LWR) -
A React/TS/JSX client that talks to Salesforce via UI API / GraphQL / Lightning Out / a Heroku app → React / headless
If no front-end surface is in scope, stop. Report that polish does not apply to pure Apex/Flow/metadata work and point to /sf-review.
Step 2: Select the stack profile
Each profile names the lens, the design system, and which existing personas/skills to dispatch. The registry is intentionally a table so new stacks (e.g. a future Salesforce front-end framework) drop in as one more row.
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.
- 9d ago First seen · 69 lines · 126 tokens per session scan A b2023688caa4
sf-polish is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 5d ago), licensed MIT. It adds 126 tokens to every session and 1,521 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-08-31.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
animation-principles
Apply animation principles — easing, staging, follow-through — to one specific UI motion. Use when tuning how an animation feels. For product-wide duration and easing tokens use motion-system (design-systems); for a full interaction spec use micro-interaction-spec.
refactoring-ui
Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions "my UI looks off" (or amateur/unprofessional), "fix the design", "Tailwind styling", "color palette", "visual hierarchy", "design system", "spacing scale", or "component styling". Also trigger when building consistent…