What is migrate-profile-to-permset?

A migration workflow that breaks a Salesforce Profile—a bundle of user permissions and settings—into Permission Sets and Permission Set Groups.

Use it to inspect selected profiles, decide how permissions should be grouped, and produce a rollout layout based on objects, roles, features, or a combination.

It reduces reliance on profiles while preserving permissions and the settings that Salesforce requires profiles to keep.

migrate-profile-to-permset — Command by BanibrataChatterjee

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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/migrate-profile-to-permset/github.svg)](https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/migrate-profile-to-permset)

Your own site

<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/migrate-profile-to-permset"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/migrate-profile-to-permset/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/banibratachatterjee/awesomesalesforceskills/migrate-profile-to-permset"><img src="https://agentmods.dev/badge/commands/banibratachatterjee/awesomesalesforceskills/migrate-profile-to-permset.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 534 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.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.00534
Opus 5.5	$0.00000	$0.00214
Sonnet 5.5	$0.00000	$0.00107
Haiku 4.5	$0.00000	$0.00053

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

Security

Grade A, and why

migrate-profile-to-permset 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/migrate-profile-to-permset.md · 71 lines

How it starts

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

/migrate-profile-to-permset — Decompose a Profile into Permission Sets + PSGs

Wraps agents/profile-to-permset-migrator/AGENT.md. Minimizes the profile to its mandatory residue (license, default record type, default app, page layouts, login IP/hours, session) and emits the PS + PSG layout that absorbs every migratable permission.

Step 1 — Collect inputs

Ask the user:

1. Target org alias (required — agent probes ProfileName, PermissionSet, PermissionSetGroup, object perms)?

2. Profile(s) to migrate?
   Either one profile name OR a name filter ("Sales*", "*Admin*").

3. Grouping strategy?
   Options: by-object | by-persona | by-feature | hybrid (recommended)

4. PSG composition goal? (flatten | nested-by-persona | baseline + overlays)

5. Rollout mode? (shadow-assign | cutover | parallel)

If more than 5 profiles match the filter, STOP and ask for a narrower scope — this agent processes one workstream at a time.

Step 2 — Load the agent

Read agents/profile-to-permset-migrator/AGENT.md + mandatory reads (security/profile-to-permset-strategy, admin/permission-set-groups, security/least-privilege-principles).

Step 3 — Execute the plan

Probe profile to enumerate every permission.
Classify each permission: mandatory residue (stays on profile) vs migratable (moves to PS).
Group migratable permissions per chosen strategy.
Author PermissionSet + PermissionSetGroup definitions.
Design rollout mode (shadow-assign to validate before cutover).

Step 4 — Deliver the output

Summary + confidence
Residue table (what stays on the profile and why)
PermissionSet / PermissionSetGroup list
PS definitions (metadata snippets)
PSG composition map
Rollout plan + validation queries
Process Observations
Citations

/architect-perms for a clean-slate persona redesign if residue is large
/audit-sharing after migration to verify no permission drift
/scan-security if object CRUD changed

Read the full file on GitHub · 71 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.

2mo ago First seen · 71 lines · 0 tokens per session scan A 8d37df41759e

Subscribe to this mod's changes

migrate-profile-to-permset 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 534 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.