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-order-failure-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-order-failure-triage)<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-order-failure-triage"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-order-failure-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-order-failure-triage"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-order-failure-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.00051 | $0.00947 |
| Opus 5 | $0.00026 | $0.00474 |
| Sonnet 5 | $0.00010 | $0.00189 |
| Haiku 4.5 | $0.00005 | $0.00095 |
Grade A, and why
b2c-order-failure-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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Failed-order triage
Use when the user needs failed order records, counts, affected products, or an
explanation of why a group of orders failed. Broader "checkout is down" symptoms
start with b2c-checkout-triage; some checkout failures create no order at all.
Scope and impact
Resolve instance/site with config_inspect (CLI: b2c setup inspect). Fix UTC
from/to boundaries and a comparison period. Ask for missing site/window;
do not use a demo default. Record impact and owner under the team's incident
process. Counts describe indexed orders, not all checkout attempts or conversion.
Access and tools
| Need | Toolkit path | Important limit |
|---|---|---|
| Enumerate FAILED orders | Check Admin Orders query support with scapi_search; external OCAPI Shop POST /order_search is the fallback |
SCAPI status=failed has returned HTTP 400; a response enum does not prove query support. CIP/CCAC is not a substitute for this population. |
| External request authentication | CLI b2c auth token --json or MCP's documented AM token-export helper |
Use only for the external client. SCAPI code mode has no OCAPI request helper, and its safety policy does not cover external HTTP. |
| Failure reason and correlation | logs_list_files -> discovered integration prefix -> bounded logs_get_recent |
Discover custom-* categories; error/customerror defaults can miss the payment integration. |
| Suspect product/custom attribute | Code-mode Admin reads; live schema expansion when the field is unknown | Compare selected fields on known failed/healthy IDs; Shopper execution is unsupported. |
| Suspected data writer | b2c-job-health | Inspect the execution log and actual data effects, not just job status. |
What ships with it
1 file 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.
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 · 67 lines · 51 tokens per session scan A 343d751b28a1
b2c-order-failure-triage is a skill published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (53 stars, last pushed today), licensed Apache-2.0. It adds 51 tokens to every session and 947 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-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.