design-sales-stages

design-sales-stages is a command for Claude Code from BanibrataChatterjee/AwesomeSalesforceSkills. It costs 0 tokens per session (311 once invoked), scanned A, original, Apache-2.0.

A design and review command for Salesforce Opportunity sales stages. It creates or checks the steps a deal passes through, including probabilities, forecast categories, exit requirements, guided fields, and validation rules.

In plain words
What is it for?
Design or audit stages for sales motions such as new-business SaaS, renewals, or professional services, with optional record-type and cycle-length context.
Why use it?
It helps make pipeline stages consistent and measurable, so sales forecasts and deal reviews rely on clear requirements rather than personal interpretation.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Design or audit stages for sales motions such as new-business SaaS, renewals, or professional services, with optional record-type and cycle-length context.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/banibratachatterjee/awesomesalesforceskills/design-sales-stages
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.

agentmods badge for design-sales-stages

README.md
[![agentmods](https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-sales-stages/github.svg)](https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/design-sales-stages)
Your own site
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/design-sales-stages"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-sales-stages/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.

agentmods 80×15 button for design-sales-stages

Your own site · 80×15
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/design-sales-stages"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-sales-stages.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 311 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00311
Opus 5 $0.00000 $0.00156
Sonnet 5 $0.00000 $0.00062
Haiku 4.5 $0.00000 $0.00031

Measured 12d ago against content hash be47f33f7e79, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

design-sales-stages 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 12d 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-sales-stages.md · 39 lines

What it actually says

/design-sales-stages — Design or audit Opportunity sales stages

Wraps agents/sales-stage-designer/AGENT.md. Produces a stage ladder with probabilities, forecast categories, exit criteria, Path + validation-rule gates.


Step 1 — Collect inputs

1. Mode?  design | audit
2. Target org alias (audit)?
3. Business motion (design)?  e.g. new-logo SaaS, renewal, professional services
4. Avg cycle length in days (design)?
5. Record type (optional)?

Step 2 — Load the agent

Read agents/sales-stage-designer/AGENT.md + mandatory reads, including templates/admin/validation-rule-patterns.md.

Step 3 — Execute the plan

Size the ladder → forecast-category mapping → stage-gate fields → Path + VRs → history tracking → Forecasts wiring → (audit) cross-check.

Step 4 — Deliver the output

Summary, stage-ladder table, VRs + Path, Forecasts notes, audit findings, Process Observations, citations.

Step 5 — Recommend follow-ups

  • /audit-reports for pipeline review coverage
  • /design-lead-routing for top-of-funnel alignment

What this command does NOT do

  • Does not deploy stages, VRs, or Path configs.
  • Does not build pipeline reports/dashboards.
  • Does not train sales reps.
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.

  1. 12d ago First seen · 39 lines · 0 tokens per session scan A be47f33f7e79

Subscribe to this mod's changes

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