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.
git clone --depth 1 https://github.com/BanibrataChatterjee/AwesomeSalesforceSkillsWrote 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/commands/banibratachatterjee/awesomesalesforceskills/design-path)<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.
<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>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 | $0.00000 | $0.00242 |
| Sonnet 5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
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 10d 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.
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
Step 5 — Recommend follow-ups
/design-sales-stagesif Opportunity stage ladder needs redesign before Path/audit-validation-rulesafter VRs deploy/architect-permsfor 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.
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.
- 10d ago First seen · 71 lines · 0 tokens per session scan A add7fe101b7c
design-path 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 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.