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/agentforce-testnpx skills add divingsbysangam/salesforce-compound-engineering-plugin --skill agentforce-testgit 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/agentforce-test)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/agentforce-test"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/agentforce-test.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.00161 | $0.01806 |
| Opus 5 | $0.00081 | $0.00903 |
| Sonnet 5 | $0.00032 | $0.00361 |
| Haiku 4.5 | $0.00016 | $0.00181 |
Grade A, and why
agentforce-test 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.
Copies of this mod
7 near-identical copies found in the catalogue:
- validation-rule-generate — 97% identical, 59 lines differ
- permission-set-generate — 97% identical, 60 lines differ
- apex-trigger-refactor — 95% identical, 58 lines differ
- flow-generate — 94% identical, 60 lines differ
- slds2-uplift — 94% identical, 59 lines differ
- compound-docs — 94% identical, 100 lines differ
- lightning-page-generate — 92% identical, 59 lines differ
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/agentforce-test
Principles enforced: 2 (verifiability), 1 (preserve the quality ceiling), 3 (jagged intelligence). See
PRINCIPLES.md.
Required reads
Procedure lives in sibling files, not only in this orchestrator:
-
When to use this skill — read
references/when-to-use-this-skill.mdbefore acting on this section. -
Modes — read
references/modes.mdbefore acting on this section. -
Step 0: Plan the tests (always before running) — read
references/step-0-plan-the-tests-always-before-running.mdbefore acting on this section. -
Mode A: Ad-hoc preview testing — read
references/mode-a-ad-hoc-preview-testing.mdbefore acting on this section. -
Mode B: Testing Center batch testing — read
references/mode-b-testing-center-batch-testing.mdbefore acting on this section.
What ships with it
11 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/action-execution-mode-c.md 1.9 KB
- references/capture-learnings-principle-7.md 690 B
- references/fix-loop-max-3-iterations.md 5.7 KB
- references/inspiration.md 1.3 KB
- references/mode-a-ad-hoc-preview-testing.md 4.4 KB
- references/mode-b-testing-center-batch-testing.md 4.6 KB
- references/modes.md 2.8 KB
- references/safety-verdict-mandatory-after-any-run-principle-1.md 1.5 KB
- references/step-0-plan-the-tests-always-before-running.md 2.2 KB
- references/test-file-location-convention.md 551 B
- references/when-to-use-this-skill.md 1.2 KB
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 · 57 lines · 161 tokens per session scan A e916c100239e
agentforce-test is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed today), licensed MIT. It adds 161 tokens to every session and 1,806 once invoked, about $0.0008 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…