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.
git 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/commands/jschuller/mcp-server-servicenow/triage)<a href="https://agentmods.dev/commands/jschuller/mcp-server-servicenow/triage"><img src="https://agentmods.dev/badge/commands/jschuller/mcp-server-servicenow/triage.svg" alt="Measured on agentmods" 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.00022 | $0.00556 |
| Opus 5 | $0.00011 | $0.00278 |
| Sonnet 5 | $0.00004 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
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 8d 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.
What it actually says
/servicenow:triage
Route based on $ARGUMENTS:
No arguments or general request
If $ARGUMENTS is empty, contains "what's on fire", "open", "recent", or "list":
- Run the List Recent Incidents workflow from the
triaging-incidentsskill. - Show open incidents sorted by priority, highlight any P1/P2.
Specific INC number
If $ARGUMENTS contains an INC number (e.g., "INC0010001"):
- Find the incident:
list_records(table_name="incident", query="number=$ARGUMENTS", limit=1) - Run the Investigate an Incident workflow — get full details, check CI dependencies, find similar incidents, check related problems/changes.
- Present findings with recommended actions.
Priority filter
If $ARGUMENTS contains "P1", "P2", "critical", or "high priority":
- Filter incidents by the specified priority level.
- Run the List Recent Incidents workflow with the appropriate priority filter.
Triage request
If $ARGUMENTS contains "triage", "assess", or "new":
- Run the Triage a New Incident workflow — assess impact/urgency, check CI blast radius, suggest priority and assignment.
Trend analysis
If $ARGUMENTS contains "trends", "analysis", "bulk", or "SLA":
- Run the Bulk Analysis workflow — top categories, repeat CIs, SLA breaches.
Fallback
For any other input, treat $ARGUMENTS as a search term:
list_records(table_name="incident", query="short_descriptionLIKE$ARGUMENTS^active=true", limit=10)- Present matching incidents and offer to investigate any of them.
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.
- 8d ago First seen · 39 lines · 22 tokens per session scan A 9b2f17ac34e4
triage is a command published in the GitHub repository jschuller/mcp-server-servicenow (17 stars, last pushed 3d ago), licensed MIT. It adds 22 tokens to every session and 556 once invoked, about $0.0001 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 commands, from other repositories
speckit.companion.doctor
Report on a spec's run health — unfinished steps, unjournaled tasks, step bleed, drift you can judge, a step that closed having verified nothing, a step that closed without the file it promised, and why completion did not land (read-only, retroactive, never halts).
postmortem
Deliver a structured post-mortem after incidents, mistakes, or stuck sessions. Use when the user requests a structured post-mortem after incidents, mistakes, or stuck sessions.
workflow-design
Exécuter la phase de Conception (Solutioning) - spécification technique et architecture.
type-coverage
Vérification Couverture des Types Python.
daily-standup
Génération Résumé Daily Stand-up.
debug
Diagnose Ansible playbook issues from symptoms.