field-service

field-service is a skill for Claude Code from serac-labs/serac. It costs 42 tokens per session (2,729 once invoked), scanned A, original, Apache-2.0.

A ServiceNow system for managing work performed by technicians in the field. It covers work orders, tasks, technicians, schedules, territories, locations, assets, mobile updates, and time entries.

In plain words
What is it for?
Use it to create and classify work orders, assign technicians, plan dispatches, record mobile status changes, track parts and time, and link jobs to locations or equipment.
Why use it?
It keeps customer jobs, technician assignments, schedules, and work details connected in one workflow. This reduces the need to track field operations across separate records or tools.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the servicenow plugin — 70 skills shipped together

Good fit Use it to create and classify work orders, assign technicians, plan dispatches, record mobile status changes, track parts and time, and link jobs to locations or equipment.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/serac-labs/serac/field-service
Install

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.

Any agent
npx skills add serac-labs/serac --skill field-service
Clone the repo
git clone --depth 1 https://github.com/serac-labs/serac

Made for: Claude Code.

Or install servicenow, the plugin that ships this one along with the rest of its 70 skills.

Wrote 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.

agentmods badge for field-service

README.md
[![agentmods](https://agentmods.dev/badge/skills/serac-labs/serac/field-service/github.svg)](https://agentmods.dev/skills/serac-labs/serac/field-service)
Your own site
<a href="https://agentmods.dev/skills/serac-labs/serac/field-service"><img src="https://agentmods.dev/badge/skills/serac-labs/serac/field-service/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.

agentmods 80×15 button for field-service

Your own site · 80×15
<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="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,729 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00042 $0.02729
Opus 5.5 $0.00017 $0.01092
Sonnet 5.5 $0.00008 $0.00546
Haiku 4.5 $0.00004 $0.00273

Measured 1mo ago against content hash 50516b28470f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

packages/skills/field-service/SKILL.md · 421 lines

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" },
])

Read the full file on GitHub · 421 lines

Changes

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.

  1. 1mo ago First seen · 421 lines · 42 tokens per session scan A 50516b28470f

Subscribe to this mod's changes

field-service is a skill published in the GitHub repository serac-labs/serac (78 stars, last pushed 5d 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.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.

Related

Other skills, from other repositories

sn-safe-write

Change ServiceNow data safely — plan first, apply only after review, verify, and know how to revert. Use whenever a create, update, upsert or delete on an instance is requested.

IvanBBaev/servicenow-mcp-ai · 43 tokens

sn-discover

Map a ServiceNow instance into Markdown (version and counts, custom applications, per-scope tables and artefacts) with the server's own document generator. Use when asked to discover, survey, inventory or document an instance or its custom apps.

IvanBBaev/servicenow-mcp-ai · 53 tokens

sn-triage

Triage a ServiceNow incident or a failing behaviour — instance health, recent errors, what automation runs on the table, and what changed on the record. Use when something is broken, slow or erroring on an instance.

IvanBBaev/servicenow-mcp-ai · 50 tokens

sn-uib

Review a ServiceNow UI Builder (UIB) experience or workspace page — its page map, what a change would touch, data broker security and page weight. Use when asked to explain, audit or assess a UI Builder page, workspace or experience before changing it.

IvanBBaev/servicenow-mcp-ai · 57 tokens

sn-security

Review the security posture of a ServiceNow instance — the ACL scan, hardening properties and cross-scope access — or explain why one user can or cannot read, write, create or delete a table, record or field. Use for a security review, a hardening check, or a "why can't this user see / edit it" question.

IvanBBaev/servicenow-mcp-ai · 73 tokens

sn-upgrade

Review ServiceNow upgrade readiness — the upgrade history, the skipped records an upgrade left unresolved, base vs customer versions of one skip, and store apps with an update. Use after a family or patch upgrade, before planning one, or when asked which skipped records to revert, keep or merge.

IvanBBaev/servicenow-mcp-ai · 62 tokens