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 jschuller/mcp-server-servicenow --skill triaging-incidentsgit clone --depth 1 https://github.com/jschuller/mcp-server-servicenowWrote 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/jschuller/mcp-server-servicenow/triaging-incidents)<a href="https://agentmods.dev/skills/jschuller/mcp-server-servicenow/triaging-incidents"><img src="https://agentmods.dev/badge/skills/jschuller/mcp-server-servicenow/triaging-incidents/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/jschuller/mcp-server-servicenow/triaging-incidents"><img src="https://agentmods.dev/badge/skills/jschuller/mcp-server-servicenow/triaging-incidents.svg" alt="Reviewed on agentmods" width="80" 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.00082 | $0.01863 |
| Opus 5 | $0.00041 | $0.00932 |
| Sonnet 5 | $0.00016 | $0.00373 |
| Haiku 4.5 | $0.00008 | $0.00186 |
Grade A, and why
triaging-incidents 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 5d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triaging ServiceNow Incidents
Create, triage, investigate, and analyze incidents. See references/incident-fields.md for the priority matrix, states, categories, and encoded query patterns.
Workflows
1. List Recent Incidents
Get a summary of recent incidents by priority, state, or assignment group.
Progress checklist (copy into your response):
- [ ] Query incidents with filters
- [ ] Summarize by priority and state
- [ ] Highlight critical/P1 incidents
- List recent incidents (last 24 hours, open):
list_records(table_name="incident", query="active=true^sys_created_on>=javascript:gs.daysAgoStart(1)", fields="number,short_description,priority,state,assignment_group,assigned_to,sys_created_on", limit=20, order_by="-priority") - For a specific assignment group:
list_records(table_name="incident", query="active=true^assignment_groupLIKE<group_name>", fields="number,short_description,priority,state,assigned_to", limit=20) - Summarize: total count, breakdown by priority (P1/P2/P3/P4), breakdown by state, highlight any P1/P2 incidents.
2. Triage a New Incident
Assess impact and urgency, then suggest priority, category, and assignment group.
Progress checklist:
- [ ] Get incident details
- [ ] Assess impact and urgency
- [ ] Check affected CI and its dependencies
- [ ] Suggest priority, category, assignment group
- [ ] Recommend next steps
- Get the incident details:
get_record(table_name="incident", sys_id="<incident_sys_id>") - If a CI is attached, check its relationships to assess blast radius:
get_ci(sys_id="<cmdb_ci_sys_id>") get_ci_relationships(sys_id="<cmdb_ci_sys_id>") - Look for similar recent incidents (same CI or category):
list_records(table_name="incident", query="cmdb_ci=<ci_sys_id>^sys_created_on>=javascript:gs.daysAgoStart(30)", fields="number,short_description,state,priority", limit=10) - Recommend triage decisions:
- Priority: Based on impact x urgency matrix (see
references/incident-fields.md) - Category: Based on the affected CI class and description keywords
- Assignment group: Based on CI ownership or category routing rules
- Priority: Based on impact x urgency matrix (see
- Present recommendations with reasoning.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed · +4 lines 3894a4d49de2
- 11d ago First seen · 166 lines · 82 tokens per session scan A 52298a3ab37c
triaging-incidents is a skill published in the GitHub repository jschuller/mcp-server-servicenow (17 stars, last pushed 2d ago), licensed MIT. It adds 82 tokens to every session and 1,863 once invoked, about $0.0004 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
servicenow-incident-triage
Triage a ServiceNow incident or a queue of incidents using NowAIKit MCP tools — gather context, find similar past incidents, suggest a resolution, set priority, and assign. Use when the user asks to triage, investigate, prioritize, or work an incident (by number or as a batch).
report-issue-local
File a bug or feature request against this MCP server's own repo. Use for server-specific issues — tool logic, service integrations, config problems, or domain bugs that aren't caused by the framework.
thinking-five-whys-plus
When a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.
thinking-map-territory
When a claim, doc, test, metric, or assumption conflicts with observed behavior, stop theorizing from the map and verify the live code or data; let territory overrule.
unicli-repair
Evidence-driven repair workflow for a broken Uni-CLI adapter. Trigger on a failed unicli envelope, a quarantined adapter, or an explicit adapter-repair request. Classifies non-source failures, edits only the reported adapter path, and uses the original command as a bounded oracle.
thinking-kepner-tregoe
Use when a selective defect needs IS/IS-NOT difference analysis or a consequential option choice needs must/want weighting and adverse-consequence comparison.