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/reset-source-trackinggit 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/reset-source-tracking)<a href="https://agentmods.dev/commands/forcedotcom/sf-skills/reset-source-tracking"><img src="https://agentmods.dev/badge/commands/forcedotcom/sf-skills/reset-source-tracking.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.00043 | $0.00659 |
| Opus 5 | $0.00022 | $0.00329 |
| Sonnet 5 | $0.00009 | $0.00132 |
| Haiku 4.5 | $0.00004 | $0.00066 |
Grade A, and why
reset-source-tracking 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 yesterday.
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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
WARNING — Destructive operation. Resetting source tracking tells the SF CLI to forget every tracked change between your local project and the org. After reset:
- A subsequent
sf project deploy pushwill treat all local metadata as new and deploy everything. - A subsequent
sf project retrieve startwill treat all org metadata as new and retrieve everything. - On a shared sandbox, this can trigger unintended mass deploys or retrieves that overwrite other developers' in-progress work.
Only proceed if you are on a personal scratch org or developer sandbox that you own.
Workflow
-
Resolve the target org. Parse
$ARGUMENTSfor--target-org <alias>. If not supplied, find the project's default:sf config get target-org --jsonExtract the
valuefield. If no default is set, ask the user: "Which org alias should source tracking be reset for?" -
Confirm the target. Display the resolved alias clearly, e.g.:
Target org:
myDevSandboxResetting source tracking is destructive on shared sandboxes. Typeyes, reset source tracking for myDevSandboxto continue, or anything else to cancel.Wait for the user's reply. If the response does not match
yes, reset source tracking for <alias>(case-insensitive), print "Cancelled — no changes made." and stop. -
Execute the reset:
sf project reset tracking --target-org <alias> --jsonParse the JSON result. On success the
statusfield is0andresultis an empty object{}. -
Report outcome. On success, print:
Source tracking reset for
<alias>. The CLI has cleared its local tracking state.On failure (non-zero status or an
errorkey in the JSON), surface the error message verbatim so the user can diagnose. -
Post-reset guidance. Recommend previewing the full diff before deploying:
Run
sf project deploy preview --target-org <alias> --jsonto review everything that will be pushed to the org before you deploy.
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.
- yesterday First seen · 48 lines · 43 tokens per session scan A 887aa77fbc32
reset-source-tracking is a command published in the GitHub repository forcedotcom/sf-skills (961 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 659 once invoked, about $0.0002 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.