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-sobject-create-configuregit 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-sobject-create-configure)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/field-service-sobject-create-configure"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/field-service-sobject-create-configure/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-sobject-create-configure"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/field-service-sobject-create-configure.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.00074 | $0.03293 |
| Opus 5 | $0.00037 | $0.01647 |
| Sonnet 5 | $0.00015 | $0.00659 |
| Haiku 4.5 | $0.00007 | $0.00329 |
Grade A, and why
field-service-sobject-create-configure 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 3d 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 — 272 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Managing Sfs Sobject Create
When to Use This Skill
Create sObject records via Headless 360 REST API. Describes the flow (describe → query → create), Field Service data model DAG, field requirements, insertion order, and common pitfalls. Reference when creating Skill, WorkType, SkillRequirement, or other Field Service sObjects.
Workflow
Create an sObject record via headless-360
Be helpful — understand business context before creating records. Consider the business domain of the sObject being created and iterate through short, structured questions (ask/why/impact) until no ambiguities remain that would change what gets created. Skip questions when answers are already obvious from context or existing data.
Flow
Phase 1: Describe — dispatch_readonly GET /services/data/v67.0/sobjects/<SObject>/describe
Phase 2: Query existing records — learn the org's shape...
dispatch_readonly GET /services/data/v67.0/query,
queryParams.q = "SELECT <required + picklist fields> FROM <SObject> ORDER BY CreatedDate DESC LIMIT 20".
Use it to: match naming/value conventions, see which optional fields are actually populated,
catch duplicates, and confirm write access before spending a create.
Phase 3: Create — dispatch POST to create records. Single...
Data model DAG
Example (Field Service junction pattern — same pattern applies to any sObject DAG based on the data shape):
Skill (0C5) WorkType (08q) ← roots (parallel)
└──────────┬──────────┘
SkillRequirement (0Hx) ← junction (last)
Fields and insertion order
Scan describe fields[] for createable:true (skip the rest — describe is large). Such a
field is required when also nillable:false and defaultedOnCreate:false (defaulted ones
the platform fills — omit). Two kinds:
- Scalar → put its value in the create body.
type:"reference"→ foreign key. Ifnillable:false(hard edge), create parent inreferenceTo[]first. Polymorphic refs list many — pick one. Topo-sort: roots first, pass eachidto dependents.nillable:truerefs → optional, PATCH later.
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.
- 3d ago Changed · +215 lines 83606d3e256a
- 6d ago First seen · 57 lines · 74 tokens per session scan A 3b12aaaadeba
field-service-sobject-create-configure is a skill published in the GitHub repository forcedotcom/sf-skills (981 stars, last pushed 3d ago), licensed Apache-2.0. It adds 74 tokens to every session and 3,293 once invoked, about $0.0004 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
event-store-design
Design and implement event stores for event-sourced systems. Use when building event sourcing infrastructure, choosing event store technologies, or implementing event persistence patterns.
convex-explain-app
Explain an existing Convex app — data model + relationships, public vs internal functions, auth/ownership model, components, a request→data flow — read from the schema and function surface. Read-only.
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.
nornicdb-grpc
Drive NornicDB over gRPC — the Qdrant-compatible surface (Collections, Points, Snapshots) plus the additive NornicSearch service. Use when ingesting via Qdrant SDKs, migrating from Qdrant, or running hybrid text+vector search from a non-Bolt client. Covers connection, RPC catalog, collection→database mapping…
openloomi-api
OpenLoomi ships a local-first HTTP API served from the desktop app (port 3414, fallback 3515). All auth, Memory, AI, RAG, Loop, and Audit data live in a local SQLite database — your data stays on your machine and the OpenLoomi app is the source of truth. The only externally-routed auth path is the Composio OAuth…
nw-ddd-eventsourcing
Event Sourcing and CQRS as DDD implementation patterns — when to use, aggregate event streams, projections, snapshots, sagas, upcasting, conflict resolution.