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 serac-labs/serac --skill field-servicegit clone --depth 1 https://github.com/serac-labs/seracWrote 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/serac-labs/serac/field-service)<a href="https://agentmods.dev/skills/serac-labs/serac/field-service"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/field-service.svg" alt="Measured on agentmods" 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.00042 | $0.02729 |
| Opus 5 | $0.00021 | $0.01365 |
| Sonnet 5 | $0.00008 | $0.00546 |
| Haiku 4.5 | $0.00004 | $0.00273 |
Grade A, and why
field-service 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 — 421 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Field Service Management for ServiceNow
Field Service Management (FSM) manages work orders, technician dispatch, and mobile field operations.
FSM Architecture
Work Order (wm_order)
├── Work Order Tasks (wm_task)
│ ├── Time Entries
│ └── Parts Used
├── Asset/CI
└── Location
Dispatch
├── Scheduling
└── Route Optimization
Key Tables
| Table | Purpose |
|---|---|
wm_order |
Work orders |
wm_task |
Work order tasks |
wm_resource |
Field technicians |
wm_schedule_entry |
Schedule entries |
wm_territory |
Service territories |
Work Orders (ES5)
Create Work Order
// Create work order (ES5 ONLY!)
var workOrder = new GlideRecord("wm_order")
workOrder.initialize()
// Basic info
workOrder.setValue("short_description", "HVAC repair - Building A")
workOrder.setValue("description", "AC unit not cooling properly")
workOrder.setValue("priority", 2)
// Classification
workOrder.setValue("work_order_type", "repair")
workOrder.setValue("category", "hvac")
// Location
workOrder.setValue("location", locationSysId)
workOrder.setValue("cmdb_ci", hvacUnitCISysId)
// Customer/Contact
workOrder.setValue("account", customerAccountSysId)
workOrder.setValue("contact", contactSysId)
// Scheduling
var scheduledStart = new GlideDateTime()
scheduledStart.addDaysLocalTime(1)
workOrder.setValue("scheduled_start", scheduledStart)
// Assignment
workOrder.setValue("assignment_group", fieldServiceGroupSysId)
// SLA
workOrder.setValue("sla", slaDefinitionSysId)
workOrder.insert()
Work Order Tasks
// Create work order tasks (ES5 ONLY!)
function createWorkOrderTasks(workOrderSysId, tasks) {
var createdTasks = []
for (var i = 0; i < tasks.length; i++) {
var task = new GlideRecord("wm_task")
task.initialize()
task.setValue("work_order", workOrderSysId)
task.setValue("short_description", tasks[i].description)
task.setValue("order", (i + 1) * 100)
// Estimated duration
task.setValue("estimated_duration", tasks[i].duration)
// Skills required
if (tasks[i].skills) {
task.setValue("skills", tasks[i].skills)
}
// Parts needed
if (tasks[i].parts) {
task.setValue("u_parts_required", tasks[i].parts)
}
var taskSysId = task.insert()
createdTasks.push({
sys_id: taskSysId,
number: task.getValue("number"),
})
}
return createdTasks
}
// Example
createWorkOrderTasks(workOrderSysId, [
{ description: "Diagnose AC unit", duration: "01:00:00", skills: "hvac_certified" },
{ description: "Replace compressor", duration: "02:00:00", parts: "COMP-AC-001" },
{ description: "Test and verify", duration: "00:30:00" },
])
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 · 421 lines · 42 tokens per session scan A 50516b28470f
field-service is a skill published in the GitHub repository serac-labs/serac (78 stars, last pushed 13d ago), licensed Apache-2.0. It adds 42 tokens to every session and 2,729 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
design-inventory
Use to run the Claude Design to ClosedLoop pipeline against the current web-ui. Stage A inventories a design export zip into schema-validated findings (typed design units - screens, regions like nav bars, standalone components like a chat dialog; UX and behavioral changes; Storybook component reuse mapping; token…
prd-creator
This skill helps PMs draft lightweight PRDs. It should be used when a PM wants to define a new feature, brainstorm requirements, or prep for sprint planning. Triggers include "I have a feature idea", "help me write a PRD", "let's break this into stories", or "what do I need for sprint planning". Optimized for speed …
cross-repo-cache
Check if cross-repo coordinator results can be reused, avoiding redundant Sonnet agent launches. Compares peer repo git hashes against stored hashes from last coordinator run. Triggers on: entering Phase 1.4.1, checking cross-repo cache, before discovering peers. Returns CROSSREPOCACHEHIT with cached status or…
team
Org-level agent team designer via epic team CLI (cross-project, append-merge). Subcommands: list, show, sync, link, unlink, history. Use when setting up agents, designing teams, or /spec yields 3+ requirements.
tasks
A task-breakdown tool that turns a plan, specification, feature brief, bug report, technical-debt item, or chore into small TASK-NNN work items. Technical debt means postponed cleanup or design work in a codebase.
continue
Autonomous work — find and execute ready tasks.