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 IvanBBaev/servicenow-mcp-ai --skill sn-upgradegit clone --depth 1 https://github.com/IvanBBaev/servicenow-mcp-aiWrote 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/ivanbbaev/servicenow-mcp-ai/sn-upgrade)<a href="https://agentmods.dev/skills/ivanbbaev/servicenow-mcp-ai/sn-upgrade"><img src="https://agentmods.dev/badge/skills/ivanbbaev/servicenow-mcp-ai/sn-upgrade/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/ivanbbaev/servicenow-mcp-ai/sn-upgrade"><img src="https://agentmods.dev/badge/skills/ivanbbaev/servicenow-mcp-ai/sn-upgrade.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00062 | $0.00730 |
| Opus 5.5 | $0.00025 | $0.00292 |
| Sonnet 5.5 | $0.00012 | $0.00146 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
sn-upgrade 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 2d 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 — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sn-upgrade — what the upgrade skipped, and what to do with it
Read-only analysis through the ServiceNow MCP server.
When not to use
- Something broke after the upgrade and users see it now — start with sn-triage, then come back for the skips.
- Comparing two instances or reviewing an update set — use sn-drift.
- Reverting, merging or resolving a skip on the instance — this skill only reads; the change itself goes through sn-safe-write.
- Hand-off (where the client has the plugin's subagents): a skip list too
long to read in the conversation goes to the
sn-investigatorsubagent, which returns the classified records without flooding the context.
Steps
- Packages: this skill calls tools from
instance,artifactsanddocs, which the defaultdiscoveryprofile leaves off. ReadenabledPackagesinservicenow_get_status; for a missing package, enable it with the server'senable_packageadmin tool and tell the user, or ask the operator to add it toSN_TOOL_PACKAGES. A package listed indeniedPackagescannot be enabled — skip the steps that need it and report them as not checked. - History:
servicenow_review_upgradewith no arguments lists the upgrades, newest first (from / to version, dates, completion status). Take thesys_idof the upgrade in question. - Skipped records:
servicenow_review_upgradewithupgrade— the unresolved skips grouped by application and artefact type. A skip already reviewed (retained, merged, reverted) is not listed. - Per skip: for the records that matter most — security, business rules,
script includes, client scripts first —
servicenow_review_upgradewithupdate_name.only_customer_changeskeeps the customer version;only_base_changescan revert to the new base;both_changedneeds a merge — show the field diff.servicenow_get_artifactreads the current record when the diff alone does not explain the customisation. - Store apps:
servicenow_review_upgradewithstore_updates: true— apps with an update and the customised artefacts in their scope that the update can overwrite. - To keep the result:
servicenow_document_instancewithkinds: ["upgrade"]writesupgrade.md.
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.
- 2d ago First seen · 58 lines · 62 tokens per session scan A 0ced7b43610d
sn-upgrade is a skill published in the GitHub repository IvanBBaev/servicenow-mcp-ai (8 stars, last pushed yesterday), licensed MIT. It adds 62 tokens to every session and 730 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-10-15.
Other skills, from other repositories
instance-performance-triage
Answer "the instance is slow" or "my nightly job never ran" from ServiceNow's own telemetry — transaction logs, syslog, systrigger, progress workers, execution trackers — instead of ad-hoc scripts that add to the load.
change-rollback
Undo a change already written to a ServiceNow instance — recover the prior payload from sysupdateversion, write it back without corrupting it, and know which damage update set back-out, Deleted Records, or nothing at all can reverse.
blast-radius
Trace ServiceNow configuration dependencies — what artifacts touch a given field, what calls a script include, table/app-level config inventory. Use before deletes, renames, or refactors.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.
problem-management
Manage ServiceNow problems — create from linked incidents, proactive pattern detection, RCA with 5-Whys, knownerror workarounds (KEDB), KEDB search by CI/category/keywords, and permanent-fix linkage to changes.
debugging-mutations
Verify what changed on a ServiceNow instance after a tool call — sysaudit inspection, syslog/transaction logs, session context, Flow Designer execution logs, outbound HTTP traces.