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-data-capture-form-designer-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-data-capture-form-designer-configure)<a href="https://agentmods.dev/skills/forcedotcom/sf-skills/field-service-data-capture-form-designer-configure"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/field-service-data-capture-form-designer-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-data-capture-form-designer-configure"><img src="https://agentmods.dev/badge/skills/forcedotcom/sf-skills/field-service-data-capture-form-designer-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.00195 | $0.02357 |
| Opus 5 | $0.00097 | $0.01179 |
| Sonnet 5 | $0.00039 | $0.00471 |
| Haiku 4.5 | $0.00019 | $0.00236 |
Grade A, and why
field-service-data-capture-form-designer-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 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 — 111 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Design a Data Capture Form (from prose or from an image / PDF)
This skill produces an intermediate JSON spec from the user's input — a
natural-language description or a PDF/image of an existing form — gets the
user's approval on the plan, and then invokes fs-data-capture-form-deployer to
compile and deploy.
When this skill fires
The user asks for a Data Capture Flow / Field Service Mobile form. The input arrives in one of two modes:
- Prose mode — the user describes the form in plain text with no attached file. Examples:
- "Create a data capture form for asset inspection that asks for asset id, condition rating, photos, and remarks."
- "Build a Field Service form for inventory transfer with parts repeater, source location, and destination dropdown."
- "Generate a DataCaptureFlow that captures three things: site name, contact info, and a notes field."
- Image / PDF mode — the user supplies a path to a
.pdf,.png,.jpg, or.jpegfile. Examples:- "Convert /tmp/inspection.pdf to a Data Capture Flow"
- "Build a Field Service form from this image: ~/Downloads/site-visit.png"
- "Turn this paper form into a DataCaptureFlow" (with attached image)
Detect the mode from the input: if the user supplied a .pdf / .png / .jpg / .jpeg path, use image/PDF mode; otherwise use prose mode. Everything after extraction (steps 2-6) is identical for both.
Workflow
1. Read the source (mode-dependent)
Prose mode — read the description carefully; don't fabricate fields. Extract only the fields the user actually mentioned. Don't invent extra fields based on what "usually goes on" an inspection form. If the user says "asks for asset id, condition rating, photos, and remarks", emit four fields, not eight.
If the user's description is too vague to produce a usable form ("build a form that captures stuff about a service appointment"), ask one or two targeted questions before extracting — what fields they want, whether there's a parent record, what should happen on submit. Don't guess.
What ships with it
2 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.
- 7d ago First seen · 111 lines · 195 tokens per session scan A 46dc45327666
field-service-data-capture-form-designer-configure is a skill published in the GitHub repository forcedotcom/sf-skills (987 stars, last pushed yesterday), licensed Apache-2.0. It adds 195 tokens to every session and 2,357 once invoked, about $0.0010 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
expo-design-system
Framework (OSS). Build and maintain a design system inside an Expo app - a reusable theme of design tokens (color, spacing, typography, radius, shadow, motion), reusable component structure with variant/size/state prop conventions, and rules for when to extract a repeated view into a shared component. Use when…
flutter-build-responsive-layout
Use LayoutBuilder, MediaQuery, or Expanded/Flexible to create a layout that adapts to different screen sizes. Use when you need the UI to look good on both mobile and tablet/desktop form factors.
display-glasses-with-jetpack-compose-glimmer
Provides guidelines for developing projected Android XR apps for display glasses using the Jetpack Compose Glimmer UI toolkit. This skill covers foundational Glimmer design principles, workflows for implementing Jetpack Compose Glimmer, and interaction models for the glasses form factor. Use this skill to build an…
omh-apple-design
This is a Hermes-native apple-design workflow skill.
axiom-audit-liquid-glass
Use when the user mentions Liquid Glass review, iOS 26 UI updates, toolbar improvements, or visual effect migration.
axiom-audit-ux-flow
Use when the user mentions UX flow issues, dead-end views, dismiss traps, missing empty states, broken user journeys, or wants a UX audit of their iOS app.