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.
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 microsoft/sre-agent --skill servicenow-change-managementgit clone --depth 1 https://github.com/microsoft/sre-agentWrote 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/microsoft/sre-agent/servicenow-change-management)<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.
<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>- 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.00067 | $0.00759 |
| Opus 5 | $0.00034 | $0.00380 |
| Sonnet 5 | $0.00013 | $0.00152 |
| Haiku 4.5 | $0.00007 | $0.00076 |
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 11d 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 — 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, oremergencyfor active customer-impacting fixes.implementation_plan/riskas appropriate.- Capture the returned change
number(e.g.CHG0030042),sys_id, and the ready-to-use clickablelinkthe tool returns. Surface the CR in the Artifacts & links section as a markdown hyperlink[<number>](<link>)using that returnedlink— never the bare CHG number, which is not clickable. (Do not try to build the URL from aSERVICENOW_URLenv var — it is not available in the agent environment; the tool already returns the full clickablelink.)
- Attach the RCA with
UploadServiceNowAttachment:table_sys_id: the Change Requestsys_idfrom 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.
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.
- 11d ago First seen · 52 lines · 67 tokens per session scan A b045612413fc
servicenow-change-management is a skill published in the GitHub repository microsoft/sre-agent (154 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 759 once invoked, about $0.0003 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.