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 skills add SalesforceCommerceCloud/b2c-developer-tooling --skill b2c-checkout-triagegit clone --depth 1 https://github.com/SalesforceCommerceCloud/b2c-developer-toolingWrote 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/salesforcecommercecloud/b2c-developer-tooling/b2c-checkout-triage)<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-checkout-triage"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-checkout-triage/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-checkout-triage"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-checkout-triage.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00049 | $0.00950 |
| Opus 5 | $0.00024 | $0.00475 |
| Sonnet 5 | $0.00010 | $0.00190 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
b2c-checkout-triage 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.
How it starts
The opening of the file, as written. The whole thing — 69 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checkout and payment triage
Outcome: quantify the observed symptom, localize a likely subsystem, and produce an actionable handoff. Do not create test orders, charge/refund payments, change order status, or modify production data as part of inspection.
Scope and impact
Use config_inspect (CLI: b2c setup inspect) and confirm site, UTC time window,
reported symptom, and comparison period. Ask for missing values. Preserve the
same target/window in all calls. No cartridge source is required.
"Orders down" can mean less traffic, checkout errors, abandoned baskets, payment declines, or delayed reporting. Failed order records alone do not measure all checkout attempts or conversion. Do not force every incident into a payment cause. Record breadth, duration, workaround, and owner. Follow the team's severity and update process for live customer impact; do not wait for exact counts to escalate.
Access and tools
| Signal | Preferred path | Limit / fallback |
|---|---|---|
| Payment/custom logs | logs_list_files, then logs_get_recent on discovered prefixes |
Start with 20 relevant entries; samples are not full-window counts. CLI: b2c logs list / b2c logs get. |
| Order records | Discover Admin Orders contracts via code mode | A response enum does not establish supported status filters. See failed-order triage for the demonstrated OCAPI fallback. |
| Affected products/attributes | SCAPI Admin product reads; live schemas for tenant custom fields | Compare known IDs and selected fields. Shopper contracts are reference-only in this runtime. |
| Suspected import/integration | b2c-job-health | Read the chosen job's log and check its actual data effects. |
| Traffic/latency context | Code mode Metrics where enabled; CLI b2c metrics |
Feature access and scopes vary. CIP/CCAC is a separate reporting path: CLI b2c cip, with freshness/coverage limits. |
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 · 69 lines · 49 tokens per session scan A 05d6d4dd796a
b2c-checkout-triage is a skill published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (53 stars, last pushed today), licensed Apache-2.0. It adds 49 tokens to every session and 950 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-12.
Other skills, from other repositories
code_explorer
Explores the repository to locate primary source files, coupled UI components, and test files for bug reports or feature requests.
session-investigator
Investigate fast-agent session and history files to diagnose issues. Use when a session ended unexpectedly, when debugging tool loops, when correlating sub-agent traces with main sessions, or when analyzing conversation flow and timing. Covers session.json metadata, history JSON format, message structure, tool…
smiles-validation
Strict SMILES validation, structural comparison, and modification verification. Catches invalid LLM-generated molecules.
dd-triage-flaky-test
Load when investigating a specific flaky test. Gets history, failure pattern, and category, then recommends fix, quarantine, or escalate.
atmos-schemas
JSON Schema for Atmos: stack-manifest and atmos.yaml config schemas, IDE auto-completion, validate stacks/schema/config, SchemaStore integration.
dd-symdb
Symbol Database - search service symbols, find probe-able methods.