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 my-servicenow-skillgit 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/my-servicenow-skill)<a href="https://agentmods.dev/skills/jschuller/mcp-server-servicenow/my-servicenow-skill"><img src="https://agentmods.dev/badge/skills/jschuller/mcp-server-servicenow/my-servicenow-skill/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/my-servicenow-skill"><img src="https://agentmods.dev/badge/skills/jschuller/mcp-server-servicenow/my-servicenow-skill.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00048 | $0.00560 |
| Opus 5.5 | $0.00019 | $0.00224 |
| Sonnet 5.5 | $0.00010 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
my-servicenow-skill 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 4d 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.
What it actually says
My ServiceNow Skill
One paragraph: the job this skill does, for whom, and what it never does (for example "read-only: it recommends changes and makes none").
Tables and roles
| Table | What it gives | Readable with |
|---|---|---|
incident |
What you read from it | The least role that can read it |
Declare every table your tool calls read in io.github.jschuller/servicenow-tables, and the roles in io.github.jschuller/servicenow-roles. If the skill calls a write tool, add io.github.jschuller/servicenow-writes with its name. Test the skill on a developer instance with an identity that holds exactly those roles.
When access is denied
- 403 on a table: not assessable with this identity. Say which table and which role it needs. More access means another identity configured in the server; never ask for credentials in the conversation.
- 0 rows or fields missing from every row (
list_recordsadds awarning): possibly hidden by an ACL. Don't report "nothing found" as a fact. aggregate_recordsrefused (401 under API-key auth): count fromlist_recordsrows instead.
Workflow
Progress checklist:
- [ ] Step one
- [ ] Step two
- [ ] Report, separating facts from recommendations
- Write each tool call in a code block, as a call, so the validator can check it:
list_records(table_name="incident", query="active=true^priority<=2", fields="number,short_description,priority,active", limit=20) - Put long reference material in
references/and link to it: see the notes. - Say what the report contains.
Tips
- Request every field you filter on in
fields=, so a hidden field shows up in the warning. - Write in your own words, and cite ServiceNow's documentation by link (see
references/notes.md).
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.
- 4d ago First seen · 50 lines · 48 tokens per session scan A ad7306422a97
my-servicenow-skill is a skill published in the GitHub repository jschuller/mcp-server-servicenow (24 stars, last pushed 4d ago), licensed MIT. It adds 48 tokens to every session and 560 once invoked, about $0.0002 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-10-14.
Other skills, from other repositories
swag
This skill should be used when the user says "add proxy config", "create reverse proxy", "SWAG config", "nginx proxy", "expose service", "proxy configuration", "subdomain config", "subfolder config", "configure SWAG", "list proxy configs", "view proxy config", "edit proxy config", "remove proxy config", "check proxy…
scholar-workflow
Use when the user asks you to search, retrieve, or reason about scholarly sources — papers, patents, books, or standards — guides tool selection, chaining, and cross-domain workflows.
cor-api-tools
Deep reference for all 61 COR MCP API tools — complete argument listings, JSON request/response examples, and common usage patterns for every module.
cor-auth
Authentication cheat sheet for the COR MCP Server — covers both auth modes (email/password and client credentials) step by step, token refresh mechanism, and common auth errors.
cor-mcp-server
Main skill for the COR MCP Server — a comprehensive MCP server that exposes 61 Project COR API tools via FastMCP with dual auth (email/password or client credentials), stdio/SSE transport, and auto-refreshing OAuth 2.0.
cor-mcp-setup
Set up and use the COR MCP Server — 61 tools for Project COR (projects, tasks, clients, time tracking, teams). Covers both auth modes: email/password and API key + client secret.