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 field-service-setup-orchestrator-getgit 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/field-service-setup-orchestrator-get)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/field-service-setup-orchestrator-get"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/field-service-setup-orchestrator-get/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/field-service-setup-orchestrator-get"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/field-service-setup-orchestrator-get.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.00107 | $0.00745 |
| Opus 5 | $0.00053 | $0.00373 |
| Sonnet 5 | $0.00021 | $0.00149 |
| Haiku 4.5 | $0.00011 | $0.00075 |
Grade A, and why
field-service-setup-orchestrator-get 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 7d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
How It Works
This skill is the entry point for all Field Service setup. It identifies what the user wants to configure and routes to the correct sub-skill. It does not perform setup work itself.
Phase 1 — Identify and Confirm
If the intent is unclear or generic, first establish what the user wants to set up before going further.
Before routing to any workflow, always ask a brief confirmation question — never skip this step, even when intent is obvious or the user has already provided data. Adapt the question naturally to context:
- For workflows with a design stage (Foundation Setup, Scheduling Policy, Data Capture Forms): the question should establish whether the user wants a guided design conversation or to proceed directly with data they already have.
- For workflows without a design stage (Pre-Work Brief, Mobile Branding): confirm the user is ready before proceeding.
One short question. Wait for the answer before delegating.
Phase 2 — Route
Match the user's intent semantically to a workflow and delegate to the sub-skill.
| Workflow | Sub-skill | Note |
|---|---|---|
| Foundation Setup (default) | sfs-setup-experience/sfs-foundation-setup-designer → deploys via sfs-sobject-create |
Always first; covers Work Types, Skills, Service Territories, Operating Hours |
| Scheduling Policy | sfs-setup-experience/sfs-scheduling-policy-designer → deploys via sfs-sobject-create |
Ask if Foundation is done; if not, offer it first |
| Data Capture Forms | sfs-mobile-core-experience/fs-data-capture-form-designer → fs-data-capture-form-deployer |
Ask if Foundation is done; if not, offer it first |
| Pre-Work Brief | sfs-frontline-ai/fs-prework-brief-deployer |
Ask if Foundation is done; if not, offer it first |
| Mobile Branding | sfs-mobile-core-experience/fs-mobile-branding |
Ask if Foundation is done; if not, offer it first |
Conversational Tone
- Announce each phase in one plain sentence before it begins — what's about to happen and why.
- Never expose skill names, SOR IDs, or tool references to the user (no "sfs-foundation-setup-designer", "sfs-sobject-create", "dispatch"). Use plain labels: "Foundation Setup", "design interview", "creating your records".
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.
- 7d ago First seen · 49 lines · 107 tokens per session scan A dfce5f58bdb5
field-service-setup-orchestrator-get is a skill published in the GitHub repository forcedotcom/sf-skills (987 stars, last pushed yesterday), licensed Apache-2.0. It adds 107 tokens to every session and 745 once invoked, about $0.0005 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-05.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…