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-commitnpx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill sf-commitgit clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-pluginWhat 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.00090 | $0.00590 |
| Opus 5 | $0.00045 | $0.00295 |
| Sonnet 5 | $0.00018 | $0.00118 |
| Haiku 4.5 | $0.00009 | $0.00059 |
Grade A, and why
sf-commit 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sf-commit
Produce well-structured commit messages following Salesforce-flavored conventional commit format.
<feature_description> #$ARGUMENTS </feature_description>
Salesforce Angle
- Type/scope examples:
feat(apex):,fix(lwc):,feat(flow):,chore(metadata):,feat(integration):,fix(data):,chore(permset):,chore(profile):. - Don't include attribution footers in incremental commits — only on the final ship commit (per V3 ce-commit convention).
- Stage only files relevant to this logical Salesforce unit (avoid
git add -Ato prevent picking up unrelated metadata).
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
This skill follows the standard sf-compound-engineering execution discipline:
- Understand the input — read the
<feature_description>block above and any referenced files, plans, or issues. - Plan a small set of phases — break the work into 2-5 ordered steps that an implementer (or another skill) can verify.
- Apply the Salesforce Angle notes above — these encode the platform-specific considerations (governor limits, sharing context, deploy ordering, FLS, metadata semantics) that distinguish this skill from generic counterparts.
- Use Salesforce-aware contexts and commands — file paths under
force-app/main/default/..., test commands likesf apex run test, deploy commands likesf project deploy validateandsf project deploy start, query the org withsf data querywhen state inspection is needed. - Surface decisions back to the user — when a step requires a choice that materially affects scope or risk, ask using the platform's blocking question tool rather than guessing.
Related
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 · 39 lines · 90 tokens per session scan A c08301152fef
sf-commit is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 5d ago), licensed MIT. It adds 90 tokens to every session and 590 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-08-31.
Other skills, from other repositories
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…