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-experience-cloud)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/design-experience-cloud"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-experience-cloud/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-experience-cloud"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/design-experience-cloud.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.00536 |
| Opus 5 | $0.00000 | $0.00268 |
| Sonnet 5 | $0.00000 | $0.00107 |
| Haiku 4.5 | $0.00000 | $0.00054 |
Grade A, and why
design-experience-cloud 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.
How it starts
The opening of the file, as written. The whole thing — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/design-experience-cloud — Design or audit an Experience Cloud site admin setup
Wraps agents/experience-cloud-admin-designer/AGENT.md. Produces template choice, audience model, member license + PSG composition, sharing set decisions, guest-user posture, CMS/branding plan, login flow, and moderation rules.
Step 1 — Collect inputs
Ask the user:
1. Mode? design | audit
2. Target org alias (required — agent probes Networks, Profiles, PS/PSGs, Sharing Sets)?
3. Scenario? customer-portal | partner-community | help-center | b2b-storefront | guest-microsite | other
4. Member license type(s)? (Customer Community, Customer Community Plus, Partner Community, External Identity, guest)
5. Authentication? (SSO | login+password | self-register | passwordless | SMS OTP | guest-only)
6. Sensitivity of exposed data? (public | authenticated-only | pii | phi | pci)
If scenario is vague or license type is unstated, STOP.
Step 2 — Load the agent
Read agents/experience-cloud-admin-designer/AGENT.md + mandatory reads (admin/experience-cloud-setup, admin/sharing-sets, security/guest-user-hardening, integration/sso-patterns).
Step 3 — Execute the plan
- Choose template per scenario.
- Design audience model (branches, overrides).
- Compose profile + PSGs per audience.
- Decide sharing-set vs criteria-based-sharing-set vs share group.
- Harden guest user access (min-permissions posture).
- Plan CMS + branding workflow.
- Design login flow + self-registration + SSO.
- Author moderation rules.
Step 4 — Deliver the output
- Summary + confidence
- Template + audience model
- PS/PSG design per audience
- Sharing decisions
- Guest posture (explicit "denies access to X")
- CMS + branding plan
- Login flow
- Moderation rules
- Audit findings (audit mode)
- Process Observations
- Citations
Step 5 — Recommend follow-ups
/scan-securityon Apex/LWC exposed to the site/audit-sharingbefore go-live/architect-permsif PSG composition needs redesign
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 · 77 lines · 0 tokens per session scan A c17bed45bdba
design-experience-cloud 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 536 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.