A read-only comparison process for ServiceNow environments or saved snapshots. It finds configuration differences between places such as development, testing, and production, or shows what an update set would change.

Use it to review dev, test, and production differences, inspect an update set, or compare an instance with a saved baseline. It highlights security-related differences and their likely reconciliation.

Configuration can drift when environments are changed separately. Comparing them reveals added, removed, and changed items before a promotion or reconciliation.

sn-drift — Skill for Claude Code by IvanBBaev/servicenow-mcp-ai

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 IvanBBaev/servicenow-mcp-ai --skill sn-drift

Clone the repo

git clone --depth 1 https://github.com/IvanBBaev/servicenow-mcp-ai

Made for: Claude Code.

Or install servicenow-mcp-ai, the plugin that ships this one along with the rest of its 8 skills, 2 agents, 3 hooks, 1 MCP server.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ivanbbaev/servicenow-mcp-ai/sn-drift/github.svg)](https://agentmods.dev/skills/ivanbbaev/servicenow-mcp-ai/sn-drift)

Your own site

<a href="https://agentmods.dev/skills/ivanbbaev/servicenow-mcp-ai/sn-drift"><img src="https://agentmods.dev/badge/skills/ivanbbaev/servicenow-mcp-ai/sn-drift/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ivanbbaev/servicenow-mcp-ai/sn-drift"><img src="https://agentmods.dev/badge/skills/ivanbbaev/servicenow-mcp-ai/sn-drift.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 46 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 609 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.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00046	$0.00609
Opus 5.5	$0.00018	$0.00244
Sonnet 5.5	$0.00009	$0.00122
Haiku 4.5	$0.00005	$0.00061

Measured 3d ago against content hash 20897725b6b7, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

sn-drift 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.

skills/sn-drift/SKILL.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

sn-drift — what differs, and where

Read-only against the instances; snapshots are written locally.

When not to use

A question about one instance only — use sn-triage, sn-impact or the sn-investigator subagent.
Promoting, committing or applying anything — this skill only reads; a change goes through sn-safe-write.
Hand-off: to judge whether an update set is safe to promote, pass its name or sys_id to the sn-change-reviewer subagent (where the client has it) and report its go / hold verdict next to the diff.

Steps

Packages: this skill calls tools from instance, updatesets and artifacts, which the default discovery profile leaves off. Read enabledPackages in servicenow_get_status; for a missing package, enable it with the server's enable_package admin tool and tell the user, or ask the operator to add it to SN_TOOL_PACKAGES. A package listed in deniedPackages cannot be enabled — skip the steps that need it and report them as not checked.
Both sides must be configured profiles: servicenow_list_instances.
Baseline: servicenow_snapshot_instance on the reference instance (optionally limited with sections or tables). A cancelled or failed snapshot resumes with resume.
Compare: servicenow_compare_instances with a and b (profile names), or from_snapshot to compare a live instance against the saved baseline. Use format: "file" for a large result.
Update sets: servicenow_list_update_sets, then servicenow_compare_update_set to see what an update set would change against the target (with_profile or with_snapshot), and servicenow_get_update_set for its records.
Drill into a difference with servicenow_get_artifact or servicenow_explain_artifact on each side.

Output

Group differences into added / removed / changed per artefact type, flag anything security-relevant (ACLs, roles, cross-scope privileges) first, and name the update set or the manual change that would reconcile each item.

Read the full file on GitHub · 52 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.

3d ago Changed 20897725b6b7
8d ago Changed · +21 lines 911687007ebb
20d ago First seen · 31 lines · 46 tokens per session scan A d4f6b9bcc4d4

Subscribe to this mod's changes

sn-drift is a skill published in the GitHub repository IvanBBaev/servicenow-mcp-ai (8 stars, last pushed yesterday), licensed MIT. It adds 46 tokens to every session and 609 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-09-27.

Backend and APIs DevOps and cloud LLM ai itsm mcp model-context-protocol servicenow

inbound-email

Handle email arriving at a ServiceNow instance — inbound email action ordering and stop-processing, the real syseventinemailaction column names, and reading sysemail when a message created no record.

serac-labs/serac · 43 tokens

mcp-tool-discovery

Find and call tools on this ServiceNow MCP server — the two meta-tools it starts with, why a missing session id makes every other tool unreachable, which queries actually match, and which advertised tools are not on the server at all.

serac-labs/serac · 53 tokens

background-script-execution

What actually happens when you call snowexecutescript — the Scripted REST endpoint Serac auto-deploys on first use, the scheduled-job fallback, what scheduledjobpending means, and how to get output back when the call comes home empty.

serac-labs/serac · 54 tokens

csdm-modeling

Pick the right ServiceNow service class under the Common Service Data Model — business service, service offering, application service, business application — and point the CMDB tools at it without creating the records CSDM tells customers to migrate away from.