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 forcedotcom/sf-skills --skill service-itsm-agentic-setup-cmdb-access-assigngit clone --depth 1 https://github.com/forcedotcom/sf-skillsWrote 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/forcedotcom/sf-skills/service-itsm-agentic-setup-cmdb-access-assign)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/service-itsm-agentic-setup-cmdb-access-assign"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/service-itsm-agentic-setup-cmdb-access-assign/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/forcedotcom/sf-skills/service-itsm-agentic-setup-cmdb-access-assign"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/service-itsm-agentic-setup-cmdb-access-assign.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- NVIDIA SkillSpector pass
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.00232 | $0.04254 |
| Opus 5 | $0.00116 | $0.02127 |
| Sonnet 5 | $0.00046 | $0.00851 |
| Haiku 4.5 | $0.00023 | $0.00425 |
Grade A, and why
service-itsm-agentic-setup-cmdb-access-assign 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 8d 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Assign a User CMDB Access (Service Cloud ITSM)
Grants a specific user the ability to read and work with CMDB (Configuration Management Database)
data by assigning the license-backed CMDB permission sets and their permission-set licenses. Every
call runs through the Salesforce-hosted Headless-360 MCP server (server key headless-360) via its
four meta-tools (discover, describe, dispatch_readonly, dispatch). The org is derived from the
OAuth JWT bound to the current MCP session — the skill never handles an org id, alias, or credentials —
so this works identically against production and sandbox with no per-user MCP install.
This is Layer 3 of CMDB setup. It assumes the org-level CMDB gate is already lifted (the feature
is ENABLED) — that is a separate skill (service-itsm-agentic-setup-cmdb-configure, Layers 0–2).
This skill grants a user access; it does not enable the feature for the org.
The gap this skill closes
Enabling the CMDB feature lifts the org-level gate, but some CMDB reads (e.g. bundleListView)
also enforce user-level access. A user with no CMDB permission sets still gets
403 FUNCTIONALITY_NOT_ENABLED ("not enabled for this user") even when the feature is correctly
ENABLED for the org. This skill assigns that user the CMDB permission sets so those reads succeed.
This skill is a no-op if the org feature is not enabled. User-level access has no effect until the org-level CMDB feature is ENABLED. If you find the org gate is still closed, stop and tell the user the CMDB feature must be turned on for the org first — see the cross-skill note at the end.
The four CMDB permission sets
Each is a license-backed Standard permission set; assigning it also requires (and this skill assigns) its permission-set license (PSL).
| Role | Permission set (Name) |
Backing PSL (DeveloperName) |
Grants |
|---|---|---|---|
| Reader | ItSrvcCnfgItmReadPermissionSet |
ItSrvcCnfgItmReadPsl |
Read CMDB configuration items |
| Owner | ItSrvcCnfgItmOwnerPermissionSet |
ItSrvcCnfgItmOwnerPsl |
Own / edit configuration items |
| Type Reader | ItSrvcCnfgItmTypReadPermissionSet |
ItSrvcCnfgItmTypReadPsl |
Read configuration-item types |
| Type Manager | ItSrvcCnfgItmTypManagerPermissionSet |
ItSrvcCnfgItmTypMgrPsl |
Manage configuration-item types |
What ships with it
1 file 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.
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.
- 8d ago First seen · 289 lines · 232 tokens per session scan A ba46c4f6b83e
service-itsm-agentic-setup-cmdb-access-assign is a skill published in the GitHub repository forcedotcom/sf-skills (987 stars, last pushed yesterday), licensed Apache-2.0. It adds 232 tokens to every session and 4,254 once invoked, about $0.0012 per session on Opus 5. 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-09-03.
Other skills, from other repositories
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.