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 skills add divingsbysangam/salesforce-compound-engineering-plugin --skill sf-agent-native-auditgit 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-agent-native-audit)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-agent-native-audit"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-agent-native-audit/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-agent-native-audit"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/sf-agent-native-audit.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.00059 | $0.00514 |
| Opus 5 | $0.00030 | $0.00257 |
| Sonnet 5 | $0.00012 | $0.00103 |
| Haiku 4.5 | $0.00006 | $0.00051 |
Grade A, and why
sf-agent-native-audit 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sf-agent-native-audit
Verify human/agent affordance parity on a Salesforce surface; flag gaps where agents have less power than UI users.
<feature_description> #$ARGUMENTS </feature_description>
Salesforce Angle
- Map each UI action to its API/CLI/MCP counterpart.
- Flag UI-only paths (e.g., setup gestures with no Metadata API equivalent) as parity gaps.
- Verify FLS/CRUD enforcement is identical across channels.
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
- Salesforce knowledge:
docs/solutions/(search via thesf-learnings-researcheragent). - Plugin conventions: see
CLAUDE.mdfor frontmatter, naming, and protected-artifact rules.
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 · 39 lines · 59 tokens per session scan A 1e2dee610c1f
sf-agent-native-audit is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 5d ago), licensed MIT. It adds 59 tokens to every session and 514 once invoked, about $0.0003 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
autoreview
Pre-commit/ship code review: Codex default; optional Claude or Pi.
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
omh-code-review
This is a Hermes-native code-review workflow skill.
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
code-reviewer
Code review specialist focused on patterns, bugs, security, and performance.
agent-teams-simplify-and-harden
Implementation + audit loop using parallel agent teams with structured simplify, harden, and document passes. Spawns implementation agents to do the work, then audit agents to find complexity, security gaps, and spec deviations, then loops until code compiles cleanly, all tests pass, and auditors find zero issues or…