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/review-update-set)<a href="https://agentmods.dev/commands/jschuller/mcp-server-servicenow/review-update-set"><img src="https://agentmods.dev/badge/commands/jschuller/mcp-server-servicenow/review-update-set/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/commands/jschuller/mcp-server-servicenow/review-update-set"><img src="https://agentmods.dev/badge/commands/jschuller/mcp-server-servicenow/review-update-set.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.00025 | $0.00510 |
| Opus 5 | $0.00013 | $0.00255 |
| Sonnet 5 | $0.00005 | $0.00102 |
| Haiku 4.5 | $0.00003 | $0.00051 |
Grade A, and why
review-update-set 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 9d 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:review-update-set
Route based on $ARGUMENTS:
No arguments
If $ARGUMENTS is empty:
- Run the List & Summarize Update Sets workflow from the
reviewing-update-setsskill. - Show update sets grouped by state (in progress, complete) with change counts.
Specific update set name
If $ARGUMENTS is a name (not a keyword like "compare" or "promote"):
- Find the update set:
list_update_sets(query="nameLIKE$ARGUMENTS", limit=5) - If one match found, run the Deep Review a Single Update Set workflow — list all changes, categorize by type, flag risky changes (ACLs, script includes, schema changes).
- If multiple matches, list them and ask the user which one to review.
Compare request
If $ARGUMENTS contains "compare":
- Ask the user for two update set names (or parse them from the arguments).
- Run the Compare Two Update Sets workflow — find overlapping records, conflicts, dependency issues.
Pre-promotion check
If $ARGUMENTS contains "promote", "promotion", "checklist", or "safe":
- Find the update set from remaining arguments.
- Run the Pre-Promotion Checklist workflow — verify state, check for Default set entries, test artifacts, risky types.
- Generate a pass/fail promotion readiness report.
Fallback
For any other input, search update sets by name:
list_update_sets(query="nameLIKE$ARGUMENTS", limit=10)- Present matches and offer to deep-review 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.
- 9d ago First seen · 37 lines · 25 tokens per session scan A f45698528eaa
review-update-set is a command published in the GitHub repository jschuller/mcp-server-servicenow (17 stars, last pushed today), licensed MIT. It adds 25 tokens to every session and 510 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
assemble-team
Assemble a pre-built agent team for parallel work - review, feature, debug, cross-platform, full-stack, or research.
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.
ia-verify
Run pre-PR verification chain -- build, types, lint, tests, security scan, diff review.
ia-test-browser
Run browser tests on pages affected by current PR or branch.
ia-agent-native-audit
Score each of the 5 agent-native principles (parity, granularity, composability, emergent capability, improvement-over-time) against a codebase and report gaps.
check-architecture
Angular Architecture Review.