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-triagegit 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-triage)<a href="https://agentmods.dev/skills/ivanbbaev/servicenow-mcp-ai/sn-triage"><img src="https://agentmods.dev/badge/skills/ivanbbaev/servicenow-mcp-ai/sn-triage/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-triage"><img src="https://agentmods.dev/badge/skills/ivanbbaev/servicenow-mcp-ai/sn-triage.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.00050 | $0.00721 |
| Opus 5.5 | $0.00020 | $0.00288 |
| Sonnet 5.5 | $0.00010 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
sn-triage 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.
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-triage — first look at a problem
Read-only. Every call goes through the ServiceNow MCP server with the active profile; nothing here writes to the instance.
When not to use
- Assessing a planned change — use sn-impact; comparing environments — use sn-drift.
- Fixing the problem — once the cause is known, the fix goes through sn-safe-write.
- Hand-off: a long, read-heavy dig (many records, flows or scripts) goes to
the
sn-investigatorsubagent (where the client has it), so the main conversation keeps only its report.
Steps
- Packages: this skill calls tools from
ops,history,scripts,flowsandcodecheck, 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. - Health: the same
servicenow_get_statusanswer (profile, write mode) andservicenow_check_capabilities(what this user can read). A missing capability explains many "empty" answers. - Symptoms:
servicenow_read_opswithkind: "syslog"andlevel: "error"for the last minutes;kind: "jobs"withfilter: "overdue"for stuck scheduled work;kind: "email_queue"for mail problems;kind: "transactions","integrations"and"mid"for slow pages, failing outbound calls and MID / ECC queue trouble. - The record:
servicenow_get_recordfor the current state, thenservicenow_get_record_historyto see who changed which field and when. - The automation that touches it:
servicenow_describe_table_logicfor the table's business rules, client scripts, UI policies, UI actions and ACLs, andservicenow_trace_table_event(operation: "update"or"insert") for the order they run in.servicenow_get_flow_runsshows flow executions for the record. - Suspect code:
servicenow_get_scriptandservicenow_lint_scripton the script the trace points at;servicenow_search_codefor an error message text.
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 714cf32b9e65
- 8d ago Changed · +21 lines 8bc235d03ef9
- 11d ago Changed · +2 lines d58b2d19184d
- 13d ago Changed 795a1c8d0fe2
- 20d ago First seen · 35 lines · 50 tokens per session scan A cfa4734403b9
sn-triage is a skill published in the GitHub repository IvanBBaev/servicenow-mcp-ai (8 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 721 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.
Other skills, from other repositories
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.
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.
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.
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.
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.
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.