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/salesforcecommercecloud/b2c-developer-tooling/update-script-api-docsgit clone --depth 1 https://github.com/SalesforceCommerceCloud/b2c-developer-toolingWhat 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.00000 | $0.00330 |
| Opus 5 | $0.00000 | $0.00165 |
| Sonnet 5 | $0.00000 | $0.00066 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade C, and why
update-script-api-docs scanned grade C with 1 finding 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 2d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf /tmp/script-api-docs-update What it actually says
Update Script API Documentation
Download the latest B2C Commerce Script API documentation from the configured sandbox and update the bundled docs in the SDK.
Steps
- Download Script API docs from the configured sandbox using
./cli docs download - Replace the markdown files in
packages/b2c-tooling-sdk/data/script-api/ - Regenerate the search index with
pnpm --filter @salesforce/b2c-tooling-sdk run generate:docs-index - Show the version extracted from
index.mdheader - Show git status/diff summary of what changed
Commands to Run
# Download to temp directory
./cli docs download /tmp/script-api-docs-update
# Check version
head -1 /tmp/script-api-docs-update/index.md
# Replace existing files
rm -f packages/b2c-tooling-sdk/data/script-api/*.md
cp /tmp/script-api-docs-update/*.md packages/b2c-tooling-sdk/data/script-api/
# Regenerate index
pnpm --filter @salesforce/b2c-tooling-sdk run generate:docs-index
# Show changes
git status packages/b2c-tooling-sdk/data/script-api/ --short
git diff packages/b2c-tooling-sdk/data/script-api/*.md --stat
# Cleanup
rm -rf /tmp/script-api-docs-update
After running, summarize:
- The Script API version (from index.md header like "# B2C Commerce Script API 26.2")
- Number of files updated
- Key changes (new classes, deprecated methods, etc.)
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.
- 2d ago First seen · 41 lines · 0 tokens per session scan C ad8a646bf9c4
update-script-api-docs is a command published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (53 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 330 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
release
Publish a new version of all packages to npm.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.