design-lead-routing

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

A Salesforce planning command for deciding who should receive each new lead based on its source, location, and product.

In plain words
What is it for?
Use it to design or review lead assignment rules, queues, territory coverage, response-time setup, and conversion handoffs.
Why use it?
It replaces ad hoc assignment decisions with a documented routing plan, including queues, territories, response targets, duplicate checking, and handoff after conversion.

Command for Claude Code

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

Good fit Use it to design or review lead assignment rules, queues, territory coverage, response-time setup, and conversion handoffs.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/design-lead-routing"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-lead-routing.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 305 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.00305
Opus 5 $0.00000 $0.00152
Sonnet 5 $0.00000 $0.00061
Haiku 4.5 $0.00000 $0.00030

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

Security

Grade A, and why

design-lead-routing 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 11d 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-lead-routing.md · 40 lines

What it actually says

/design-lead-routing — Design or audit lead routing

Wraps agents/lead-routing-rules-designer/AGENT.md. Produces a routing matrix (source × geo × product → owner), queue + assignment rule design, territory layer, SLA wiring, and conversion handoff rules.


Step 1 — Collect inputs

1. Mode?  design | audit
2. Target org alias (audit)?
3. Lead sources (design)?
4. Geographies (design)?
5. Products (optional)?
6. SLA per source (optional, minutes)?

Step 2 — Load the agent

Read agents/lead-routing-rules-designer/AGENT.md + mandatory reads.

Step 3 — Execute the plan

Dimensioned matrix → queue vs user → territory → SLA → conversion handoff → dedup ordering → (audit) rule inventory.

Step 4 — Deliver the output

Summary, routing matrix, queue + rule design, territory notes, SLA wiring, conversion rules, audit findings, Process Observations, citations.

Step 5 — Recommend follow-ups

  • /design-duplicate-rule (ordering: dedup BEFORE assignment)
  • /architect-perms for queue membership PSGs

What this command does NOT do

  • Does not activate assignment rules.
  • Does not create queues or public groups.
  • Does not build round-robin Flows.
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. 11d ago First seen · 40 lines · 0 tokens per session scan A ace0b95d9964

Subscribe to this mod's changes

design-lead-routing 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 305 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.