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-catalog-template-coordinategit 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-catalog-template-coordinate)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/service-catalog-template-coordinate"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/service-catalog-template-coordinate/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-catalog-template-coordinate"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/service-catalog-template-coordinate.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- 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.00189 | $0.03889 |
| Opus 5 | $0.00095 | $0.01945 |
| Sonnet 5 | $0.00038 | $0.00778 |
| Haiku 4.5 | $0.00019 | $0.00389 |
Grade A, and why
service-catalog-template-coordinate 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unified Catalog Service Process Coordinator
The single entry point for the Unified Catalog Service Process lifecycle: find a template, deploy one, create a Service Process from scratch, activate it, and organize it under a catalog category. Rather than hard-coding each operation's API steps, this skill discovers the platform's own guided setup recipe for the requested operation, reads that recipe's live steps, and follows them. The recipe is the source of truth — so the exact steps, ordering, and safeguards always match what the org actually enforces, and never drift from a frozen copy.
The connected org is fixed for the session — this skill takes no org alias and handles no credentials.
Scope
- In scope: Finding / browsing / ranking Service Process templates; deploying a named template; creating a Service Process from scratch; activating a Service Process; placing a Service Process under a catalog category; and running the guided end-to-end flow (find → deploy → activate). Each operation is carried out by discovering and following the platform's guided recipe for it.
- Out of scope: Authoring or editing template content; enabling the Unified Catalog feature or other
ITSM setup (a separate
service-itsm-*-configureconcern — this skill self-heals a per-user access gap but does not turn the feature on for an org that lacks the license); bulk operations; Data Cloud data kits, CRM Analytics, or App Framework catalogs.
How this skill works — discover, read, follow
Every operation runs through the headless-360 setup server, which exposes the org's guided setup recipes and the operations behind them. The loop is always the same:
- Discover the recipe for the user's operation with a plain-language query (e.g. "deploy a Unified Catalog service process from a template"). Take the top-ranked recipe.
- Describe that recipe to read its ordered steps, preconditions, and the operation behind
each step (a ready-to-call
METHOD path). - Follow the steps in order — read-only lookups first, writes only when the recipe says so — and verify with the recipe's own verify step before reporting success.
What ships with it
3 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.
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 · 264 lines · 189 tokens per session scan A 5f795ee053ff
service-catalog-template-coordinate is a skill published in the GitHub repository forcedotcom/sf-skills (987 stars, last pushed yesterday), licensed Apache-2.0. It adds 189 tokens to every session and 3,889 once invoked, about $0.0009 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.