A Salesforce planning command for designing or reviewing a guided path through record stages, such as the stages of an opportunity or case.

Use it to plan or audit Salesforce Paths for objects such as Opportunities, Leads, Cases, Contracts, Orders, or custom objects.

It turns stage requirements into clear fields, instructions, celebrations, and rules that prevent progress when required information is missing.

design-path — Command for Claude Code by BanibrataChatterjee

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.

Clone the repo

git clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkills

Made for: Claude Code.

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/commands/banibratachatterjee/awesomesalesforceskills/design-path/github.svg)](https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/design-path)

Your own site

<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/design-path"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-path/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/commands/banibratachatterjee/awesomesalesforceskills/design-path"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-path.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 483 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.00000	$0.00483
Opus 5.5	$0.00000	$0.00193
Sonnet 5.5	$0.00000	$0.00097
Haiku 4.5	$0.00000	$0.00048

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

Security

Grade A, and why

design-path 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 2mo 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.

commands/design-path.md · 71 lines

What it actually says

/design-path — Design or audit a Sales/Service Path

Wraps agents/path-designer/AGENT.md. Produces Key Fields per step, Guidance for Success text (≤ 200 chars), celebration triggers, and the validation-rule harness that gates progression.

Step 1 — Collect inputs

Ask the user:

1. Mode? design | audit

2. Target org alias (required — agent probes existing Paths + picklist values)?

3. Object? Opportunity | Lead | Case | Contract | Order | Custom Object

4. Stage picklist API name? (e.g. StageName, Status)

5. Record type (if object uses record types)?

6. Celebration condition (optional)?
   Example: "on close-won when Amount > 500000"

If the picklist has fewer than 3 values, STOP — Path is over-engineered for this.

Step 2 — Load the agent

Read agents/path-designer/AGENT.md + mandatory reads (admin/path-setup, admin/guidance-for-success, admin/validation-rule-patterns).

Step 3 — Execute the plan

Enumerate picklist values in picklist sort order.
For each value: choose Key Fields (3–5) from the record.
Author Guidance for Success (≤ 200 chars, imperative voice).
Design VR harness that enforces required-for-stage fields (with bypass Custom Permission).
Encode celebration trigger if supplied.

Step 4 — Deliver the output

Summary + confidence
Per-step table: stage, Key Fields, Guidance for Success
VR harness (pseudo-XML)
Celebration config
Audit findings (stale paths, drift, missing guidance, orphaned VRs)
Process Observations
Citations

/design-sales-stages if Opportunity stage ladder needs redesign before Path
/audit-validation-rules after VRs deploy
/architect-perms for the bypass Custom Permission

What this command does NOT do

Does not deploy Path metadata.
Does not edit the underlying picklist — if gaps exist, flags and recommends /govern-picklists.
Does not train reps on the Path UI.

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.

2mo ago First seen · 71 lines · 0 tokens per session scan A add7fe101b7c

Subscribe to this mod's changes

design-path is a command published in the GitHub repository BanibrataChatterjee/AwesomeSalesforceSkills (4 stars, last pushed 6mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 483 tokens. 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-31.

Planning

design-path next to 6 commands from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
design-pathBanibrataChatterjee/AwesomeSalesforceSkills	Command	4	6mo ago	Apache-2.0	A	0	Claude Code
checklistgithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
clarifygithub/spec-kit	Command	148k	today	MIT	A	27	Claude Code
specifygithub/spec-kit	Command	148k	today	MIT	A	13	Claude Code
analyzegithub/spec-kit	Command	148k	today	MIT	A	26	Claude Code
convergegithub/spec-kit	Command	148k	today	MIT	A	35	Claude Code
implementgithub/spec-kit	Command	148k	today	MIT	A	14	Claude Code