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 skills add divingsbysangam/salesforce-compound-engineering-plugin --skill permission-set-generategit clone --depth 1 https://github.com/divingsbysangam/salesforce-compound-engineering-pluginWrote 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/skills/divingsbysangam/salesforce-compound-engineering-plugin/permission-set-generate)<a href="https://agentmods.dev/skills/divingsbysangam/salesforce-compound-engineering-plugin/permission-set-generate"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/permission-set-generate/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/skills/divingsbysangam/salesforce-compound-engineering-plugin/permission-set-generate"><img src="https://agentmods.dev/badge/skills/divingsbysangam/salesforce-compound-engineering-plugin/permission-set-generate.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.00149 | $0.02091 |
| Opus 5 | $0.00075 | $0.01045 |
| Sonnet 5 | $0.00030 | $0.00418 |
| Haiku 4.5 | $0.00015 | $0.00209 |
Grade A, and why
permission-set-generate 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 9d 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.
This is a copy
97% identical to agentforce-test — 60 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/permission-set-generate
Principles enforced: 1 (preserve the quality ceiling — overly-broad perms are a security regression), 5 (taste — perm set names matter), 7 (institutional memory). See
PRINCIPLES.md.
Required reads
Procedure lives in sibling files, not only in this orchestrator:
-
When to use — read
references/when-to-use.mdbefore acting on this section. -
Step 0: Research (Principle 7) — read
references/step-0-research-principle-7.mdbefore acting on this section. -
Required structure — read
references/required-structure.mdbefore acting on this section. -
Section 1: Object permissions (CRUD) — read
references/section-1-object-permissions-crud.mdbefore acting on this section. -
Section 2: Field-level security (FLS) — read
references/section-2-field-level-security-fls.mdbefore acting on this section.
What ships with it
14 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/hard-constraints-principle-1.md 4.6 KB
- references/inspiration.md 885 B
- references/output-report.md 1.1 KB
- references/required-structure.md 1.7 KB
- references/section-1-object-permissions-crud.md 1.7 KB
- references/section-2-field-level-security-fls.md 1.1 KB
- references/section-3-tab-settings.md 931 B
- references/section-4-app-visibility.md 534 B
- references/section-5-user-permissions-system-permissions.md 2.5 KB
- references/section-6-apex-class-access.md 570 B
- references/section-7-page-access-visualforce.md 419 B
- references/step-0-research-principle-7.md 1.0 KB
- references/when-to-use.md 1.4 KB
- references/workflow.md 5.4 KB
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.
- 9d ago First seen · 63 lines · 149 tokens per session scan A 1e09d29a2fcd
permission-set-generate is a skill published in the GitHub repository divingsbysangam/salesforce-compound-engineering-plugin (10 stars, last pushed 5d ago), licensed MIT. It adds 149 tokens to every session and 2,091 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to agentforce-test, differing in 60 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…