agentmods.dev

design-entitlements

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

A Salesforce design command for customer entitlement processes and milestones. Entitlements define the service a customer receives, while milestones track deadlines such as response or resolution times.

In plain words
What is it for?
Use it to design or audit Salesforce support timelines, business-hour rules, account or contract coverage, and automatic entitlement assignment.
Why use it?
It makes service-level rules explicit, including what should happen when deadlines are met, approaching, or missed.

Command for Claude Code

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

not rated 4repo 6mo ago A scan 0 tokens original Apache-2.0

Good fit Use it to design or audit Salesforce support timelines, business-hour rules, account or contract coverage, and automatic entitlement assignment.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/banibratachatterjee/awesomesalesforceskills/design-entitlements
View source ↗ BanibrataChatterjee/AwesomeSalesforceSkills
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-entitlements

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/design-entitlements"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-entitlements.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 500 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.00500
Opus 5.5 $0.00000 $0.00200
Sonnet 5.5 $0.00000 $0.00100
Haiku 4.5 $0.00000 $0.00050

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

Security

Grade A, and why

design-entitlements 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-entitlements.md · 72 lines

How it starts

The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.

/design-entitlements — Design or audit Entitlement Processes + Milestones

Wraps agents/entitlement-and-milestone-designer/AGENT.md. Produces Entitlement Processes, Milestones (with time trigger formulas), Success/Warning/Violation actions, and auto-entitlement rules.

Step 1 — Collect inputs

Ask the user:

1. Mode? design | audit

2. Target org alias (required — agent probes Entitlement + Milestone metadata, BusinessHours, Contracts)?

3. SLA terms (for design)?
   - First-response time(s) by priority / channel
   - Resolution time(s) by priority / channel
   - Business-hours calendar(s) to key off

4. Entitlement-to-Account model?
   Options: per-Account | per-Contract | per-Asset | guest / public

5. Case auto-entitlement source? (email-to-case | chat | web-to-case | api)

If SLA terms are not specified, STOP.

Step 2 — Load the agent

Read agents/entitlement-and-milestone-designer/AGENT.md + mandatory reads (admin/entitlement-management, admin/business-hours-and-holidays, admin/case-escalation-rules).

Step 3 — Execute the plan

  • Probe existing Entitlement Processes + Milestones.
  • Build Process ladder per priority × channel.
  • Encode Milestone time trigger formulas (BusinessHours-aware).
  • Define Success / Warning / Violation actions (field updates, task creation, email alerts).
  • Design Entitlement Contact model if required.

Step 4 — Deliver the output

  • Summary + confidence
  • Entitlement Process design
  • Milestone table with time trigger formulas
  • Actions per milestone
  • Auto-entitlement rule logic
  • Audit findings (drift, stale processes, missing actions)
  • Process Observations
  • Citations

Step 5 — Recommend follow-ups

  • /configure-business-hours if calendars are ambiguous
  • /audit-case-escalation to verify Escalation Rules align with SLA ladder
  • /design-omni-channel if routing depends on SLA state

What this command does NOT do

Read the full file on GitHub · 72 lines

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. 2mo ago First seen · 72 lines · 0 tokens per session scan A 5927f6c89585

Subscribe to this mod's changes

design-entitlements 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 500 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
Related

design-entitlements compared with commands from other repositories

design-entitlements next to 6 commands from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
design-entitlementsBanibrataChatterjee/AwesomeSalesforceSkillsCommand46mo agoApache-2.0A0Claude Code
checklistgithub/spec-kitCommand148ktodayMITA13Claude Code
clarifygithub/spec-kitCommand148ktodayMITA27Claude Code
specifygithub/spec-kitCommand148ktodayMITA13Claude Code
analyzegithub/spec-kitCommand148ktodayMITA26Claude Code
convergegithub/spec-kitCommand148ktodayMITA35Claude Code
implementgithub/spec-kitCommand148ktodayMITA14Claude Code