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 reviewing-update-setsgit 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/reviewing-update-sets)<a href="https://agentmods.dev/skills/jschuller/mcp-server-servicenow/reviewing-update-sets"><img src="https://agentmods.dev/badge/skills/jschuller/mcp-server-servicenow/reviewing-update-sets/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/reviewing-update-sets"><img src="https://agentmods.dev/badge/skills/jschuller/mcp-server-servicenow/reviewing-update-sets.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.00077 | $0.01193 |
| Opus 5 | $0.00039 | $0.00596 |
| Sonnet 5 | $0.00015 | $0.00239 |
| Haiku 4.5 | $0.00008 | $0.00119 |
Grade A, and why
reviewing-update-sets 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 12d 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviewing ServiceNow Update Sets
Review, analyze, and compare update sets before promotion. See references/update-set-fields.md for update types, risk categories, and pre-promotion checklist fields.
Workflows
1. List & Summarize Update Sets
Get an overview of update sets by state with change counts.
Progress checklist (copy into your response):
- [ ] List update sets by state
- [ ] Get change counts for each
- [ ] Summarize by developer and state
- List update sets by state:
list_update_sets(state="in progress", limit=20) list_update_sets(state="complete", limit=20) - For each update set, get the change count:
list_update_set_changes(update_set_sys_id="<sys_id>", limit=1) - Summarize: name, state, developer, change count, last modified date.
2. Deep Review a Single Update Set
Examine all changes in an update set, categorize by type, and flag risks.
Progress checklist:
- [ ] Get update set details
- [ ] List all customer updates
- [ ] Categorize changes by type
- [ ] Flag risky changes (ACLs, script includes, schema changes)
- [ ] Summarize findings with risk assessment
- Get the update set details:
get_update_set(sys_id="<update_set_sys_id>") - List all customer updates in the set:
list_update_set_changes(update_set_sys_id="<update_set_sys_id>", limit=100) - Categorize each change by type (business rule, client script, UI policy, ACL, etc.).
- Flag risky changes — see
references/update-set-fields.mdfor risk categories:- ACL modifications (security impact)
- Script Includes (shared library changes)
- Table/Column schema changes (data model impact)
- System Properties (global configuration)
- Scheduled Jobs (background automation)
- Present a summary: total changes, breakdown by type, risk flags with explanations.
3. Compare Two Update Sets
Find overlapping records and potential conflicts between two update sets.
Progress checklist:
- [ ] Get changes for update set A
- [ ] Get changes for update set B
- [ ] Find overlapping records (same target name/table)
- [ ] Identify potential conflicts
- [ ] Report overlap and conflict details
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.
- 12d ago First seen · 129 lines · 77 tokens per session scan A ae46c9be7ad1
reviewing-update-sets is a skill published in the GitHub repository jschuller/mcp-server-servicenow (18 stars, last pushed 3d ago), licensed MIT. It adds 77 tokens to every session and 1,193 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
pr-alignment-loop
Iterate a PR to its final form by running two opposing reviewer droids (reviewer-robustness and reviewer-minimalist) in a bounded back-and-forth loop. The main orchestrator synthesizes their feedback, makes edits, runs tests, and stops when both approve, on stagnation, or after 3 rounds. Use when the user asks to…
tuicr
Use tuicr's review CLI to read and add comments in active TUI review sessions, and launch tuicr in cmux, tmux, Zellij, or Herdr when a user needs an interactive review pane.
liveagent-code-review
Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation. Use when the user asks for code review, invokes the Code Review action from Git Review, or explicitly mentions this skill.
omh-image-cards
This is a Hermes-native img-summary workflow skill.
omh-code-review
This is a Hermes-native code-review workflow skill.
omh-refactor-plan
This is a Hermes-native refactor-plan workflow skill.