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-assignment-rules)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/design-assignment-rules"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-assignment-rules/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-assignment-rules"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-assignment-rules.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.00484 |
| Opus 5.5 | $0.00000 | $0.00194 |
| Sonnet 5.5 | $0.00000 | $0.00097 |
| Haiku 4.5 | $0.00000 | $0.00048 |
Grade A, and why
design-assignment-rules 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.
How it starts
The opening of the file, as written. The whole thing — 73 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-assignment-rules — Design or audit Assignment + Auto-Response rules
Wraps agents/assignment-and-auto-response-rules-designer/AGENT.md. Produces the rule-entry table, queue design, email-template mapping, and cutover plan.
Step 1 — Collect inputs
Ask the user:
1. Mode? design | audit
2. Target org alias (required — agent probes queues, templates, and existing rules)?
3. Object? Lead | Case
4. Routing dimensions?
Any of: source, geography, product, tier, language, custom predicate
5. Auto-response scope? (yes | no — default yes for Web-to-Lead / Email-to-Case)
6. Coexistence with existing routing? (Flow | Lead Routing Rules | Omni-Channel | none)
If dimensions are unspecified, STOP and ask for the routing matrix.
Step 2 — Load the agent
Read agents/assignment-and-auto-response-rules-designer/AGENT.md + mandatory reads (admin/lead-routing, admin/case-routing, admin/queues-and-groups, admin/email-templates).
Step 3 — Execute the plan
- Probe queues, groups, email templates, existing rules.
- Build the routing matrix.
- Author the rule-entry table (order matters — first match wins).
- Map auto-response templates per rule entry.
- Emit cutover plan that coexists with existing routing.
Step 4 — Deliver the output
- Summary + confidence
- Rule-entry table (ordered)
- Queue / group design
- Email-template mapping
- Cutover plan
- Audit findings (audit mode)
- Process Observations
- Citations
Step 5 — Recommend follow-ups
/design-lead-routingif Lead Routing Rules replace part of this/design-omni-channelfor Chat/Messaging routing overlap/architect-permsfor queue-membership permission design/modernize-email-templatesif auto-response templates are stale
What this command does NOT do
- Does not deploy rules.
- Does not create queues — recommends their shape.
- Does not manage holiday / business-hours calendars (use
/configure-business-hours).
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 · 73 lines · 0 tokens per session scan A 7a74a393fe43
design-assignment-rules 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 484 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.
design-assignment-rules compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| design-assignment-rulesBanibrataChatterjee/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 |