What is servicenow-change-management?

A workflow for recording permanent incident fixes in ServiceNow, an IT service-management system, after the fix is prepared in a GitHub pull request.

Use it to create a ServiceNow Change Request, include the GitHub pull-request link and root-cause summary, and attach the investigation report.

It keeps the approved code or infrastructure fix linked to its root-cause report and change record. It also separates permanent fixes from temporary incident actions.

servicenow-change-management — Skill by microsoft/sre-agent

About the project

microsoft/sre-agent is the community repository for Azure SRE Agent, an AI assistant for diagnosing and resolving production problems and reducing routine operations work. It is for teams working on service reliability and includes documentation, discussions, videos, and hands-on labs for using the product. The catalogue skills relate to the agent's official plugins and resources.

microsoft/sre-agent · 187 stars · on GitHub

Install

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.

Any agent

npx skills add microsoft/sre-agent --skill servicenow-change-management

Clone the repo

git clone --depth 1 https://github.com/microsoft/sre-agent

Made for: Claude Code, Codex.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/microsoft/sre-agent/servicenow-change-management/github.svg)](https://agentmods.dev/skills/microsoft/sre-agent/servicenow-change-management)

Your own site

<a href="https://agentmods.dev/skills/microsoft/sre-agent/servicenow-change-management"><img src="https://agentmods.dev/badge/skills/microsoft/sre-agent/servicenow-change-management/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/microsoft/sre-agent/servicenow-change-management"><img src="https://agentmods.dev/badge/skills/microsoft/sre-agent/servicenow-change-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 67 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 759 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00067	$0.00759
Opus 5.5	$0.00027	$0.00304
Sonnet 5.5	$0.00013	$0.00152
Haiku 4.5	$0.00007	$0.00076

Measured 2mo ago against content hash b045612413fc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

servicenow-change-management 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 2mo 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.

labs/zava-learning/sre-config/agent-config/skills/servicenow-change-management/SKILL.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Zava Learning — ServiceNow Change Management

Use this skill to record a durable remediation in ServiceNow once the root cause is fixed in code or IaC. It is the single owner of ServiceNow Change Request and attachment operations, and applies after a GitHub PR has been opened (by pr-delivery) for the durable fix.

When to use

A connectivity/edge or application incident has been root-caused to an IaC (infra/) or application (src/) change, and a GitHub PR has been opened with the fix.
An operator explicitly asks to open a Change Request or attach an RCA to an existing record.

Do not raise a Change Request for live mitigations alone (deleting an NSG rule, restarting/rolling back a revision) — those are tracked as PagerDuty incident notes. The Change Request tracks the durable code/IaC fix.

Steps

Create the Change Request with CreateServiceNowChangeRequest:
- short_description: one-line summary of the change (symptom + fix).
- description: the RCA summary including the GitHub PR URL.
- change_type: normal (default), standard, or emergency for active customer-impacting fixes.
- implementation_plan / risk as appropriate.
- Capture the returned change number (e.g. CHG0030042), sys_id, and the ready-to-use clickable link the tool returns. Surface the CR in the Artifacts & links section as a markdown hyperlink [<number>](<link>) using that returned link — never the bare CHG number, which is not clickable. (Do not try to build the URL from a SERVICENOW_URL env var — it is not available in the agent environment; the tool already returns the full clickable link.)
Attach the RCA with UploadServiceNowAttachment:
- table_sys_id: the Change Request sys_id from step 1.
- file_name: e.g. rca-<symptom>.md.
- content: the full RCA report (timeline, root cause, fix, verification).
Reference the Change Request number back in the PagerDuty incident notes and the GitHub PR.

Read the full file on GitHub · 52 lines

Changes

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.

2mo ago First seen · 52 lines · 67 tokens per session scan A b045612413fc

Subscribe to this mod's changes

servicenow-change-management is a skill published in the GitHub repository microsoft/sre-agent (187 stars, last pushed 6d ago), licensed MIT. It adds 67 tokens to every session and 759 once invoked, about $0.0003 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-08-30.

Project management

servicenow-change-management next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
servicenow-change-managementmicrosoft/sre-agent	Skill	187	6d ago	MIT	A	67	Claude Code, Codex
imagegenopenai/codex	Skill	134k	today	Apache-2.0	A	113	Codex
local-ai-agentsmicrosoft/ai-agents-for-beginners	Skill	79k	yesterday	MIT	A	200	Claude Code, Codex
playwright-climicrosoft/playwright	Skill	100k	yesterday	Apache-2.0	A	19	Claude Code
browser-automationopenclaw/openclaw	Skill	394k	today	MIT	A	36	Claude Code
systematic-debuggingobra/superpowers	Skill	314k	4d ago	MIT	A	21	Claude Code
next-cache-components-adoptionvercel/next.js	Skill	143k	today	MIT	A	95	Claude Code