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-mcp-debuggergit 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-mcp-debugger)<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-mcp-debugger"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-mcp-debugger/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-mcp-debugger"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-mcp-debugger.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.00038 | $0.00985 |
| Opus 5.5 | $0.00015 | $0.00394 |
| Sonnet 5.5 | $0.00008 | $0.00197 |
| Haiku 4.5 | $0.00004 | $0.00098 |
Grade A, and why
b2c-mcp-debugger 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 15d 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.
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 — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Debugger Usage
Use for B2C server-side script debugging. Confirm the sandbox, deployed script, breakpoint, and request before starting a session.
Prerequisites
- Basic Auth for a BM user with
WebDAV_Manage_Customization: username plus password or WebDAV File Access and UX Studio access key. OAuth is unsupported. - Inspect unknown connection settings with
config_inspectand the task'sprojectDirectory; keep its default masking. Use resolved values. - Match local source and line numbers to deployed code and the site's cartridge
path. A breakpoint's
verifiedflag indicates local source mapping, not that matching code is deployed or active.
Capture and cleanup
- Call
debug_start_sessionwithprojectDirectory. UseconfigPathorinstanceNameonly to override the configured selection. Cartridge discovery defaults to that project; usecartridgeDirectoryonly for a different root. Preserve the returned session ID andresolution. - Call
debug_capture_at_breakpointwith the file, line, a bounded timeout, andauto_continue: truefor a snapshot. It arms its own breakpoint; a priordebug_set_breakpointscall is unnecessary. Use that tool for separate breakpoint management; it replaces the existing set. - Trigger the request. The capture tool's optional trigger supports GET without
custom headers; trigger authenticated or non-GET requests externally. An
external trigger must run while capture waits, not after awaiting its result.
A halted capture can return
trigger_pending: true; resume withdebug_controlwithaction: continuebefore expecting that request to finish. Do not retrigger it. - Use captured stack, variables, and expressions. For further halted inspection,
use
debug_inspectordebug_evaluate. Inspection returns stack and top-frame variables (all scopes) by default;includeselects stack, variables, or both. Useframe_index,scope, orobject_pathfor targeted inspection. Expressions can have side effects; keep evaluation within the requested scope. - Check halted threads with
debug_list_sessions, resume withdebug_controlwithaction: continue, and always calldebug_end_sessionwithclear_breakpoints: true, including after errors or timeouts. Stop any log watches started for the investigation.
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.
- 15d ago First seen · 73 lines · 38 tokens per session scan A 3e1abb826568
b2c-mcp-debugger is a skill published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (56 stars, last pushed yesterday), licensed Apache-2.0. It adds 38 tokens to every session and 985 once invoked, about $0.0002 per session on Opus 5.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-10-03.
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.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
feedback
Skill "feedback" from Hmbown/Codewhale, covering feedback, when to use, setup, workflow and non-goals.
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.