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.
npx agentmods add commands/banibratachatterjee/awesomesalesforceskills/diff-usersgit 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/diff-users)<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/diff-users"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/diff-users.svg" alt="Measured on agentmods" 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.00760 |
| Opus 5 | $0.00000 | $0.00380 |
| Sonnet 5 | $0.00000 | $0.00152 |
| Haiku 4.5 | $0.00000 | $0.00076 |
Grade A, and why
diff-users 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 5d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/diff-users — Side-by-side access comparison between two Salesforce users
Wraps agents/user-access-diff/AGENT.md. Produces a symmetric comparison across profile, PS/PSG, object CRUD, FLS, system permissions, Apex/VF grants, groups, queues, and territory — with risk flags for any asymmetric sensitive permission.
Step 1 — Collect inputs
Ask the user:
1. Target org alias (required — agent needs live-org access via `sf` CLI)?
2. User A (username or 15/18-char User.Id)?
3. User B (username or 15/18-char User.Id)?
4. Which dimensions to compare? (default: all)
Options: profile, permission-sets, object-crud, fls, system-perms,
apex-classes, vf-pages, tabs, apps, record-types,
custom-perms, groups, queues, territories
5. Include field-level security diff? (default: no)
FLS rows can exceed 10k on broad PSGs — turn on only when needed.
6. Purpose? (optional — shapes the Process Observations framing)
Options: new-hire-parity | access-review | incident-investigation
If user_a == user_b, STOP — this agent compares two different users.
If either user isn't resolvable in the target org, STOP and ask for clarification.
Step 2 — Load the agent
Read agents/user-access-diff/AGENT.md + all mandatory reads (probe recipe, admin/user-management, admin/permission-set-architecture, admin/permission-sets-vs-profiles, security/permission-set-groups-and-muting, plus the probe under agents/_shared/probes/user-access-comparison.md).
Step 3 — Execute the plan
Follow the agent's 6-step plan:
- Resolve both users to
User.Id. - Run
agents/_shared/probes/user-access-comparison.mdfor both users, flattening PSG components into effective PS sets. - Compute symmetric diffs per dimension (identical / only_a / only_b).
- Apply the P0/P1/P2 risk rubric.
- Frame Process Observations per the supplied
purpose. - Emit the report.
Step 4 — Deliver the output
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.
- 5d ago First seen · 85 lines · 0 tokens per session scan A 210c6c6159c9
diff-users 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 760 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.