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 Knuckles-Team/servicenow-api --skill servicenow-change-managementgit clone --depth 1 https://github.com/Knuckles-Team/servicenow-apiWrote 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/knuckles-team/servicenow-api/servicenow-change-management)<a href="https://agentmods.dev/skills/knuckles-team/servicenow-api/servicenow-change-management"><img src="https://agentmods.dev/badge/skills/knuckles-team/servicenow-api/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/knuckles-team/servicenow-api/servicenow-change-management"><img src="https://agentmods.dev/badge/skills/knuckles-team/servicenow-api/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.00137 | $0.01408 |
| Opus 5 | $0.00068 | $0.00704 |
| Sonnet 5 | $0.00027 | $0.00282 |
| Haiku 4.5 | $0.00014 | $0.00141 |
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 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 — 131 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ServiceNow Change Management
Domain-typed access to the ServiceNow Change API — the whole change-request lifecycle (normal / standard / emergency) plus tasks, schedules, CI associations, models, standard-change templates, risk calculation, conflict detection, and approval.
When to use
- Query change requests, their tasks, schedules, associated CIs, or conflicts.
- Create a normal change, or spin one from a standard-change template.
- Update a change / change-task; move to the next state.
- Run CAB flow: calculate risk → conflict check → approve.
When NOT to use
- Incidents →
servicenow-incident-management. - CMDB CI records / relationships / lifecycle →
servicenow-cmdb(this skill only associates existing CIs to a change). - Generic CRUD on arbitrary tables →
servicenow-table-api.
Prerequisites & environment
Connect via the mcp-client skill against the servicenow-api MCP server.
| Variable | Required | Notes |
|---|---|---|
SERVICENOW_INSTANCE |
✅ | Instance URL (alias SERVICENOW_URL) |
SERVICENOW_USERNAME |
✅ | Basic-auth user |
SERVICENOW_PASSWORD |
✅ | Basic-auth password |
SERVICENOW_CLIENT_ID / SERVICENOW_CLIENT_SECRET |
optional | OAuth2 |
SERVICENOW_SSL_VERIFY |
optional | TLS verification toggle |
Full env/tag matrix (do not re-document here): the mcp-client reference
agent-tools/mcp-client/references/servicenow-api.md. MCP_TOOL_MODE
(condensed|verbose|both) selects the condensed surface (used below) vs. the
one-to-one verbose tools.
Tools & actions
Prefer the condensed tool servicenow_change_management; it takes action +
a params_json JSON string whose keys are passed straight to the client
method. Actions grouped by lifecycle stage:
Query / read
get_change_requests, get_change_request, get_change_request_nextstate,
get_change_request_schedule, get_change_request_tasks, get_change_request_ci,
get_change_request_conflict, get_change_request_models,
get_change_request_worker, get_standard_change_request_templates,
get_standard_change_request_template, get_standard_change_request_model
What ships with it
2 files 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 · 131 lines · 137 tokens per session scan A 49aa842e730f
servicenow-change-management is a skill published in the GitHub repository Knuckles-Team/servicenow-api (19 stars, last pushed 14d ago), licensed MIT. It adds 137 tokens to every session and 1,408 once invoked, about $0.0007 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
change-request
ITIL change request and CAB review workflow. This skill should be used when the user asks to "create a change request", "write an RFC", "plan a change", "CAB review", "change management", "schedule maintenance", "server migration plan", "upgrade plan", "AI model deployment", "GitOps change", or describes any planned…
itil
ITIL (Version 5) framework reference for IT service management and digital product management. This skill should be used when handling incidents, creating change requests, conducting CAB reviews, classifying priority levels, asking about ITIL v5 practices, AI governance, SRE integration, error budgets, or…
tdx-tickets
This skill should be used when the user asks about TeamDynamix tickets, incidents, service requests, or work orders. Common queries include "create a ticket", "find my open tickets", "ticket status", "assign a ticket", "update a support ticket", "submit a service request", "check on my help desk request", "search for…
tdx-navigation
This skill should be used when the user wants to interact with TeamDynamix (TDX), including tickets, assets, people, or knowledge base articles. It must be activated before any domain-specific TDX tools are available. Common queries include "search for a TDX ticket", "look up an asset in TeamDynamix", "find a person…
tdx-people
This skill should be used when the user asks about people, users, or contacts in TeamDynamix. Common queries include "find a person", "look up who someone is", "search for an employee", "find someone's email address", "get a user's UID for assignment", "directory lookup".
teamdynamix
Use this skill when the user needs TeamDynamix ITSM operations through MCP: ticket triage and updates, KB article maintenance, asset/CI relationships, service catalog lookups, project issue/risk workflows, or time entry queries. Always discover IDs first, use read-before-write patterns, and enforce write safety gates.