A tool for finding and running CIP warehouse reports or SQL queries. CIP is a company analytics warehouse covering sales, products, promotions, payments, traffic, inventory, and technical trends.

Use it to answer sales and merchandising questions, inspect inventory or payment trends, and analyse API, controller, or other operational data.

It helps you locate the right report or table, handle warehouse access, limit result sizes, and interpret the correct site and date scope instead of guessing at data.

b2c-mcp-cip — Skill by SalesforceCommerceCloud/b2c-developer-tooling

Install

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.

Any agent

npx skills add SalesforceCommerceCloud/b2c-developer-tooling --skill b2c-mcp-cip

Clone the repo

git clone --depth 1 https://github.com/SalesforceCommerceCloud/b2c-developer-tooling

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-mcp-cip/github.svg)](https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-mcp-cip)

Your own site

<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-mcp-cip"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-mcp-cip/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-mcp-cip"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/b2c-mcp-cip.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 43 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,352 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00043	$0.01352
Opus 5.5	$0.00017	$0.00541
Sonnet 5.5	$0.00009	$0.00270
Haiku 4.5	$0.00004	$0.00135

Measured 15d ago against content hash d22e54166ca1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

b2c-mcp-cip 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.

packages/b2c-dx-mcp/skills/b2c-mcp-cip/SKILL.md · 89 lines

How it starts

The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CIP analytics

Use CIP for warehouse analytics: sales, products, promotions, search, payments, traffic, inventory, and API/controller trends. Use SCAPI for current records; logs/metrics for immediate diagnosis. Read this skill once through resources or skills_read (mcp/b2c-mcp-cip), then pass skillRead: true to cip_query. Discovery needs no acknowledgment.

Choose and discover

cip_discover defaults to report search; use query for task terms, then action: "report", name for parameters, tables used, and available result notes. The catalog is offline.
Prefer a curated report when its dimensions/filters answer the question. Preview SQL with params only when adapting the report or checking a definition absent from its notes; a standard report does not need a preview before running.
For custom analysis, action: "tables", query: "ccdw_aggr_%" lists live metadata; action: "table", name returns columns. Narrow names/schema and reuse findings. These calls require CIP access. Columns default to 50 per page (lists: 20). Follow nextOffset only for needed columns, not to exhaust unrelated metadata.
cip_query accepts either report plus string-valued params, or sql. Do not invent parameters or use a narrower report that omits requested evidence.

Configuration and access

Reuse projectDirectory / instanceName and resolved configuration. Requires tenantId, Account Manager clientId and clientSecret; no instance hostname or SCAPI short code is needed. Authentication is managed; do not obtain tokens. CIP supports client credentials only, not user/SLAS/JWT flows. The client needs the Salesforce Commerce API role with the selected tenant in its tenant filter; the SDK requests SALESFORCE_COMMERCE_API:<tenant>.

Tenants ending _prd use production analytics; other tenants use staging analytics. staging: true / SFCC_CIP_STAGING=true forces staging; configured cipHost / SFCC_CIP_HOST takes precedence. Staging analytics is a service destination, not permission to switch the user's target instance. Non-production data requires Reports & Dashboards data tracking enabled on supported 26.1+ environments. No data or rejected access does not establish zero sales or a healthy system.

Read the full file on GitHub · 89 lines

Changes

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 · 89 lines · 43 tokens per session scan A d22e54166ca1

Subscribe to this mod's changes

b2c-mcp-cip is a skill published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (56 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 1,352 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.

Analytics and metrics b2c cli dx

developer-tools

CLI tools, SDKs, and developer experience patterns.

miles990/claude-software-skills · 13 tokens

feishu

Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.

Hmbown/CodeWhale · 33 tokens

interview

Ask one useful structured question at a time only when material product/implementation choices are genuinely missing; remember answers and produce a brief/spec. Discoverable facts should be investigated instead of asked.

Hmbown/CodeWhale · 40 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

atmos-config

Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.