Borrowing it
Nothing to install: this file belongs to SalesforceCommerceCloud/b2c-developer-tooling. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SalesforceCommerceCloud/b2c-developer-tooling/main/.claude/skills/cli-command-development/SKILL.mdgit 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/cli-command-development)<a href="https://agentmods.dev/skills/salesforcecommercecloud/b2c-developer-tooling/cli-command-development"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/cli-command-development/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/cli-command-development"><img src="https://agentmods.dev/badge/skills/salesforcecommercecloud/b2c-developer-tooling/cli-command-development.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Rogue Agent · line 345 Skill modifies its own code, configuration, or behavior at runtime. Self-modification enables an agent to escalate privileges, disable safety constraints, or install persistent backdoors.Fix: Prevent the skill from modifying its own code, SKILL.md, or configuration files. Treat skill files as read-only at runtime.
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.00052 | $0.02749 |
| Opus 5.5 | $0.00021 | $0.01100 |
| Sonnet 5.5 | $0.00010 | $0.00550 |
| Haiku 4.5 | $0.00005 | $0.00275 |
Grade A, and why
cli-command-development 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 2d 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 — 359 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLI Command Development
This skill covers creating new CLI commands and topics for the B2C CLI.
Command Organization
Commands live in packages/b2c-cli/src/commands/. The directory structure maps directly to command names:
commands/
├── code/
│ ├── deploy.ts → b2c code deploy
│ ├── activate.ts → b2c code activate
│ └── list.ts → b2c code list
├── sandbox/
│ ├── create.ts → b2c sandbox create
│ └── list.ts → b2c sandbox list
└── mrt/
└── env/
└── var/
└── set.ts → b2c mrt env var set
Command Class Hierarchy
Choose the appropriate base class based on what your command needs:
BaseCommand (logging, JSON output, error handling)
└─ OAuthCommand (OAuth authentication)
├─ InstanceCommand (B2C instance: hostname, code version)
│ ├─ CartridgeCommand (cartridge path + filters)
│ ├─ JobCommand (job execution helpers)
│ └─ WebDavCommand (WebDAV root directory)
├─ MrtCommand (Managed Runtime API)
└─ OdsCommand (On-Demand Sandbox API)
Import from @salesforce/b2c-tooling-sdk/cli:
import { InstanceCommand, CartridgeCommand, OdsCommand } from '@salesforce/b2c-tooling-sdk/cli';
Standard Command Template
/*
* Copyright (c) 2025, Salesforce, Inc.
* SPDX-License-Identifier: Apache-2
* For full license text, see the license.txt file in the repo root
*/
import {Args, Flags} from '@oclif/core';
import {InstanceCommand} from '@salesforce/b2c-tooling-sdk/cli';
import {getApiErrorMessage} from '@salesforce/b2c-tooling-sdk';
import {t} from '../../i18n/index.js';
interface MyCommandResponse {
success: boolean;
data: SomeType[];
}
export default class MyCommand extends InstanceCommand<typeof MyCommand> {
static description = t('commands.topic.mycommand.description', 'Human-readable description');
static enableJsonFlag = true;
static examples = [
'<%= config.bin %> <%= command.id %> arg1',
'<%= config.bin %> <%= command.id %> --flag value',
'<%= config.bin %> <%= command.id %> --json',
];
static args = {
name: Args.string({
description: 'Description of the argument',
required: true,
}),
};
static flags = {
myFlag: Flags.string({
char: 'm',
description: 'Flag description',
default: 'defaultValue',
}),
myBool: Flags.boolean({
description: 'Boolean flag',
default: false,
}),
};
async run(): Promise<MyCommandResponse> {
// Validation - call appropriate require* methods
this.requireServer();
// Access parsed args and flags
const {name} = this.args;
const {myFlag, myBool} = this.flags;
this.log(t('commands.topic.mycommand.working', 'Working on {{name}}...', {name}));
// Implementation
const {data, error, response} = await this.instance.ocapi.GET('/some/endpoint');
if (error) {
this.error(t('commands.topic.mycommand.error', 'Failed: {{message}}', {
message: getApiErrorMessage(error, response),
}));
}
const result: MyCommandResponse = {
success: true,
data,
};
// JSON mode returns the object directly (oclif handles serialization)
if (this.jsonEnabled()) {
return result;
}
// Human-readable output
this.log('Success!');
return result;
}
}
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.
- 2d ago Changed · +11 lines 14dd574fd199
- 1mo ago First seen · 348 lines · 52 tokens per session scan A 8aa3ccc50bf1
cli-command-development is a skill published in the GitHub repository SalesforceCommerceCloud/b2c-developer-tooling (56 stars, last pushed yesterday), licensed Apache-2.0. It adds 52 tokens to every session and 2,749 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-08-30.
Other skills, from other repositories
developer-tools
CLI tools, SDKs, and developer experience patterns.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
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.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…