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 taurgis/sfcc-dev-mcp --skill sfcc-webdav-workflowsgit clone --depth 1 https://github.com/taurgis/sfcc-dev-mcpWrote 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/taurgis/sfcc-dev-mcp/sfcc-webdav-workflows)<a href="https://agentmods.dev/skills/taurgis/sfcc-dev-mcp/sfcc-webdav-workflows"><img src="https://agentmods.dev/badge/skills/taurgis/sfcc-dev-mcp/sfcc-webdav-workflows/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/taurgis/sfcc-dev-mcp/sfcc-webdav-workflows"><img src="https://agentmods.dev/badge/skills/taurgis/sfcc-dev-mcp/sfcc-webdav-workflows.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00056 | $0.01249 |
| Opus 5 | $0.00028 | $0.00624 |
| Sonnet 5 | $0.00011 | $0.00250 |
| Haiku 4.5 | $0.00006 | $0.00125 |
Grade A, and why
sfcc-webdav-workflows 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 9d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SFCC WebDAV Workflows
WebDAV is SFCC’s “remote filesystem over HTTP”. It’s central to:
- Moving data in/out via IMPEX
- Reading logs
- Managing catalogs/images in supported folders
This skill focuses on practical workflows and the most common permission and path pitfalls.
Quick Checklist
[ ] Confirm which auth path you are using: BM user (Basic Auth) vs API client (client-id/secret token)
[ ] For IMPEX, ensure the BM role includes File Transfer Manager access
[ ] If using API client auth, generate credentials in Account Manager
[ ] Verify directory permissions are configured in Business Manager for the exact folder(s)
[ ] Avoid overlapping WebDAV client permission paths (SFCC restriction)
[ ] Don’t expect write access to restricted folders (e.g. security logs)
[ ] For automation: scope access to the minimum folders required
Mental Model
- WebDAV ≈ HTTP interface to instance folders (not your local repo)
- Permissions are folder-scoped and configured in Business Manager
- Two common authentication modes:
- Business Manager users: Basic Auth (username/password), governed by Role permissions
- API clients: token-based auth (client credentials from Account Manager), governed by “WebDAV Client Permissions” JSON
- Wildcard folder permissions (like
/catalogs/*or “all other folders”) grant access to future subfolders automatically - WebDAV versioning is not enabled in SFCC
- Primary instance group vs sandbox: primary instance group access requires authenticated WebDAV; sandboxes often use WebDAV for manual file moves
Common SFCC WebDAV Folders (What They’re Typically For)
These vary by project, but the patterns are stable:
| Folder | Typical use | Read/Write? |
|---|---|---|
/impex/src/ |
Upload import feeds, export results | Usually read/write |
/impex/src/logs/ |
Some log exports and job artifacts | Often read |
/Logs/ |
Log files (application logs) | Usually read |
/catalogs/ |
Catalog assets (shared library content, images) | Often read |
/cartridges/ |
Code deployment via WebDAV (teams vary) | Usually read/write for deployment users |
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.
- 9d ago First seen · 112 lines · 56 tokens per session scan A 13580239a356
sfcc-webdav-workflows is a skill published in the GitHub repository taurgis/sfcc-dev-mcp (28 stars, last pushed 3d ago), licensed MIT. It adds 56 tokens to every session and 1,249 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-08-30.
Other skills, from other repositories
nebula-logger-instrumentation
Use this skill when the user wants to add or update Nebula Logger instrumentation in Apex, LWC, Aura, Flow, or OmniStudio. Covers logging APIs, save patterns, record association, scenarios, tags, async transaction linking, and save method selection.
nebula-logger-best-practices
Use this skill when the user wants to review, harden, or standardize Nebula Logger usage across a Salesforce team. Covers operational logging standards, environment-aware settings, limit-aware design, and governance guardrails.
nebula-logger-console
Use this skill when the user wants to browse, filter, or investigate Nebula Logger data in the Salesforce UI. Covers the Logger Console app, list views on Logc / LogEntryc / LogEntryTagc / LoggerScenarioc / LoggerTagc, related-list navigation, the Log record page and its LWCs, and how admins and support engineers use…
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).