servicenow-incident-management

servicenow-incident-management is a skill for Claude Code, Codex from Knuckles-Team/servicenow-api. It costs 133 tokens per session (1,145 once invoked), scanned A, original, MIT.

A set of operations for handling incidents in ServiceNow, an IT service-management system for tracking problems and support requests.

In plain words
What is it for?
Use it to triage active incidents, retrieve an incident by its ID, or open one with details such as description, urgency, impact, and caller.
Why use it?
It gives agents incident-specific ways to list, inspect, and create records instead of relying on generic database operations.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to triage active incidents, retrieve an incident by its ID, or open one with details such as description, urgency, impact, and caller.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/knuckles-team/servicenow-api/servicenow-incident-management
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 Knuckles-Team/servicenow-api --skill servicenow-incident-management
Clone the repo
git clone --depth 1 https://github.com/Knuckles-Team/servicenow-api

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.

agentmods badge for servicenow-incident-management

README.md
[![agentmods](https://agentmods.dev/badge/skills/knuckles-team/servicenow-api/servicenow-incident-management/github.svg)](https://agentmods.dev/skills/knuckles-team/servicenow-api/servicenow-incident-management)
Your own site
<a href="https://agentmods.dev/skills/knuckles-team/servicenow-api/servicenow-incident-management"><img src="https://agentmods.dev/badge/skills/knuckles-team/servicenow-api/servicenow-incident-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.

agentmods 80×15 button for servicenow-incident-management

Your own site · 80×15
<a href="https://agentmods.dev/skills/knuckles-team/servicenow-api/servicenow-incident-management"><img src="https://agentmods.dev/badge/skills/knuckles-team/servicenow-api/servicenow-incident-management.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 133 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,145 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00133 $0.01145
Opus 5 $0.00067 $0.00573
Sonnet 5 $0.00027 $0.00229
Haiku 4.5 $0.00013 $0.00114

Measured 12d ago against content hash 5a4b41183220, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

servicenow-incident-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.

servicenow_api/skills/servicenow-incident-management/SKILL.md · 97 lines

How it starts

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

ServiceNow Incident Management

Domain-typed access to the ServiceNow Incident table (incident) for ITSM triage and intake. Prefer these tools over raw table CRUD — they carry the incident field conventions and return incident-shaped records.

When to use

  • List / triage active incidents (e.g. ordered by priority).
  • Fetch a single incident by sys_id.
  • Create a new incident (short_description + urgency/impact/caller_id).

When NOT to use

  • Generic CRUD on any other table → servicenow-table-api.
  • Change requests, CMDB CIs, or knowledge articles → their dedicated skills (servicenow-change-management, servicenow-cmdb, servicenow-knowledge).
  • Bulk state transitions or fields the typed tool doesn't expose → fall back to servicenow-table-api against the incident table.

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; it takes action + a params_json JSON string whose keys are passed straight to the client method.

Condensed tool Actions
servicenow_incidents get_incidents, get_incident, create_incident

Key parameters

  • sys_id — required for get_incident.
  • data — object of field→value for create_incident (short_description, urgency, impact, caller_id, …).
  • Query/pagination controls (sysparm_query, sysparm_fields, sysparm_limit, sysparm_offset, sysparm_display_value) follow Table-API encoded-query syntax — see servicenow-table-api for the cheat-sheet.

Read the full file on GitHub · 97 lines

Files

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.

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.

  1. 12d ago First seen · 97 lines · 133 tokens per session scan A 5a4b41183220

Subscribe to this mod's changes

servicenow-incident-management is a skill published in the GitHub repository Knuckles-Team/servicenow-api (19 stars, last pushed 14d ago), licensed MIT. It adds 133 tokens to every session and 1,145 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.

Related

Other skills, from other repositories

incident-response-skill

A skill that uses object-style tool references with purpose descriptions and required flags, plus strict validation.

agentfront/frontmcp · 24 tokens

servicenow-expert

Expert in ServiceNow platform development, scripting, workflows, Service Portal, CMDB, ITSM modules, and integrations. Use when the user mentions ITSM, ITOM, workflow, automation, CMDB, or service portal, or when the task involves ServiceNow Platform, Development Components, Scripting APIs, or GlideRecord Query and…

personamanagmentlayer/pcl · 75 tokens

servicenow-ticket

Create a ServiceNow incident via the Table API. Requires SERVICENOWINSTANCE, SERVICENOWUSER, and SERVICENOWPASSWORD environment variables on the server. Trigger on: create a ServiceNow incident, raise an ITSM ticket, log an incident.

sarveshtalele/mcp-skills-registry · 59 tokens

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.

selfagency/teamdynamix-mcp · 70 tokens

tdx-knowledge-base

This skill should be used when the user asks about TeamDynamix knowledge base articles or documentation. Common queries include "search the KB", "find a knowledge article", "create documentation", "write a how-to article", "find instructions for", "look up a FAQ", "browse KB categories".

chatt-state/teamdynamix-mcp-server · 69 tokens

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…

chatt-state/teamdynamix-mcp-server · 81 tokens