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/security-guidenpx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill security-guidegit 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/security-guide)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/security-guide"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/security-guide.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.00012 | $0.00293 |
| Opus 5 | $0.00006 | $0.00147 |
| Sonnet 5 | $0.00002 | $0.00059 |
| Haiku 4.5 | $0.00001 | $0.00029 |
Grade A, and why
security-guide 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 4d 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.
What it actually says
Salesforce Security Guide
SCOPE: UNIVERSAL - This skill applies to ALL Salesforce development requiring security considerations. READ this skill for Apex (CRUD/FLS), LWC (XSS), Integrations (OAuth), and AppExchange security reviews.
Complete reference for implementing security best practices in Salesforce development.
Required reads
Procedure lives in sibling files, not only in this orchestrator:
- CRUD/FLS Enforcement — read
references/crud-fls-enforcement.mdbefore acting on this section. - Sharing Model — read
references/sharing-model.mdbefore acting on this section. - SOQL Injection Prevention — read
references/soql-injection-prevention.mdbefore acting on this section. - XSS Prevention — read
references/xss-prevention.mdbefore acting on this section. - Sensitive Data Handling — read
references/sensitive-data-handling.mdbefore acting on this section. - Security Headers (Experience Cloud) — read
references/security-headers-experience-cloud.mdbefore acting on this section. - Hosted MCP Server Security — read
references/hosted-mcp-server-security.mdbefore acting on this section. - Security Checklist — read
references/security-checklist.mdbefore acting on this section.
What ships with it
8 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/crud-fls-enforcement.md 2.5 KB
- references/hosted-mcp-server-security.md 1.6 KB
- references/security-checklist.md 634 B
- references/security-headers-experience-cloud.md 486 B
- references/sensitive-data-handling.md 1.1 KB
- references/sharing-model.md 979 B
- references/soql-injection-prevention.md 1005 B
- references/xss-prevention.md 585 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.
- 4d ago First seen · 28 lines · 12 tokens per session scan A 4f39de3f1126
security-guide is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed today), licensed MIT. It adds 12 tokens to every session and 293 once invoked, about $0.0001 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
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…