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 commands/forcedotcom/sf-skills/startgit clone --depth 1 https://github.com/forcedotcom/sf-skillsWrote 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/commands/forcedotcom/sf-skills/start)<a href="https://agentmods.dev/commands/forcedotcom/sf-skills/start"><img src="https://agentmods.dev/badge/commands/forcedotcom/sf-skills/start.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.00064 | $0.00481 |
| Opus 5 | $0.00032 | $0.00241 |
| Sonnet 5 | $0.00013 | $0.00096 |
| Haiku 4.5 | $0.00006 | $0.00048 |
Grade A, and why
start 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 today.
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
You are launching the Test Drive engine through /salesforce-test-drive:start — this plugin's
single command and entry point.
Parse $ARGUMENTS: an optional test-drive id to launch directly (skip the menu), and an optional
--instrument flag. Then read the engine and follow it exactly, start to finish:
echo "PLUGIN_ROOT=${CLAUDE_PLUGIN_ROOT}"
cat "${CLAUDE_PLUGIN_ROOT}/references/engine.md"
PLUGIN_ROOT echoed above is this plugin's absolute path, already resolved by Claude Code here in the
command. Remember that value and pass it to the engine as PLUGIN_ROOT. The engine reads its
catalog, prompts, and instrumentation spec from <PLUGIN_ROOT>/…; substitute this absolute path wherever
it does. Do not type the literal ${CLAUDE_PLUGIN_ROOT} into a Bash command — that token only
resolves inside a command body like this one, not in the engine's text, and your Bash shell has no such
variable (it would expand to an empty string and break the path).
- If
$ARGUMENTSnamed anid, run the engine withSELECTED_DRIVEset to that id (Step 3 skips the menu). - Otherwise run the engine with
SELECTED_DRIVEempty — Step 3 presents the catalog menu and lets the user choose. - Pass the
--instrumentflag through to the engine's Step 5.
The engine owns all of the logic (companion check, toolchain preflight, org detection, tiered provisioning, requirements gate, launch, handoff). Do not reimplement any of it here.
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.
- today First seen · 41 lines · 64 tokens per session scan A 9ea42d7a46a4
start is a command published in the GitHub repository forcedotcom/sf-skills (961 stars, last pushed yesterday), licensed Apache-2.0. It adds 64 tokens to every session and 481 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-09-03.
Other commands, from other repositories
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
no-vibe
Enter no-vibe mode in OpenCode (tutor mode, no direct project file writes).
learn
LEARN MODE - Explains concepts with a gentle, Socratic, and human-like coaching persona.
OPSX: Onboard
Guided onboarding - walk through a complete OpenSpec workflow cycle with narration.
debrief
Post-engagement lessons learned analysis and debrief report.