servicenow-atlas: Skill for Claude Code

.agents/skills/atlas-add-tool/SKILL.md

atlas-add-tool is a skill for Claude Code, Codex from sagar-shirwalkar/servicenow-atlas. It costs 50 tokens per session (1,026 once invoked), scanned A, original, Apache-2.0.

A coding guide for adding a callable MCP tool to the atlas filesystem or document-search server. It covers the tool definition, input fields, handler, and registration.

In plain words
What is it for?
Use it when creating a tool for document search, file listing, file reading, or another feature that must be callable by an AI model.
Why use it?
It gives a consistent pattern for exposing a new capability to an AI agent without changing unrelated server code.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is sagar-shirwalkar/servicenow-atlas's own configuration. It tells Claude Code and Codex how to work on servicenow-atlas itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything servicenow-atlas configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sagar-shirwalkar/servicenow-atlas. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sagar-shirwalkar/servicenow-atlas/main/.agents/skills/atlas-add-tool/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/sagar-shirwalkar/servicenow-atlas

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 atlas-add-tool

README.md
[![agentmods](https://agentmods.dev/badge/skills/sagar-shirwalkar/servicenow-atlas/atlas-add-tool/github.svg)](https://agentmods.dev/skills/sagar-shirwalkar/servicenow-atlas/atlas-add-tool)
Your own site
<a href="https://agentmods.dev/skills/sagar-shirwalkar/servicenow-atlas/atlas-add-tool"><img src="https://agentmods.dev/badge/skills/sagar-shirwalkar/servicenow-atlas/atlas-add-tool/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 atlas-add-tool

Your own site · 80×15
<a href="https://agentmods.dev/skills/sagar-shirwalkar/servicenow-atlas/atlas-add-tool"><img src="https://agentmods.dev/badge/skills/sagar-shirwalkar/servicenow-atlas/atlas-add-tool.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,026 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.
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.00050 $0.01026
Opus 5 $0.00025 $0.00513
Sonnet 5 $0.00010 $0.00205
Haiku 4.5 $0.00005 $0.00103

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

Security

Grade A, and why

atlas-add-tool 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.

.agents/skills/atlas-add-tool/SKILL.md · 132 lines

How it starts

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

When to use

  • User asks to "add a new tool", "create a tool for X", "expose Y as an MCP tool"
  • User is building a new capability that needs to be callable by an LLM
  • User wants to understand the existing tool registration pattern

Not for

  • General code changes outside tool definitions
  • Modifying the embedder or chunker internals
  • Changing the MCP server lifecycle (startup, shutdown, transport)

Prerequisites

Read the existing tool implementations in:

  • atlas/rag_server.py — tools on the RAG server (semantic search, etc.)
  • atlas/fs_server.py — tools on the filesystem server (read, list, search, etc.)

Workflow

1. Locate the right server file

Tool belongs to Server file
Document search / RAG atlas/rag_server.py
File listing / reading atlas/fs_server.py
Build / maintenance Consider a new server or atlas/doctor.py

2. Follow the existing pattern

Each tool has three parts in the server file:

a) Tool docstring + @server.list_tools() handler

@server.list_tools()
async def list_tools() -> list[Tool]:
    return [
        # existing tools ...
        Tool(
            name="your_tool_name",
            description="What the tool does — be specific",
            inputSchema={
                "type": "object",
                "properties": {
                    "param_name": {
                        "type": "string",
                        "description": "What this parameter is for",
                    },
                },
                "required": ["param_name"],
            },
        ),
    ]
  • Tool names: snake_case, conventionally matching the function name.
  • Descriptions: written for an LLM reader. Include edge cases, defaults, and example values.
  • Parameters: use JSON Schema types (string, integer, array, etc.). Mark required explicitly.

b) The @server.call_tool() handler branch

@server.call_tool()
async def call_tool(name: str, arguments: dict) -> list[TextContent]:
    if name == "your_tool_name":
        result = await your_handler(arguments)
        return [TextContent(type="text", text=result)]
    elif name == "existing_tool":
        ...

Read the full file on GitHub · 132 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.

  1. 12d ago First seen · 132 lines · 50 tokens per session scan A 64216774fdfb

Subscribe to this mod's changes

atlas-add-tool is a skill published in the GitHub repository sagar-shirwalkar/servicenow-atlas (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 1,026 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-31.

Related

Other skills, from other repositories

servicenow-cmdb

ITOM CMDB operations on the ServiceNow CMDB + CI Lifecycle Management APIs via the servicenow-api MCP server — query configuration items by class, read a CI with its attributes and relations, create/update/patch CI instances, manage CI relationships, and drive the CI lifecycle (status, actions, leases, operators). Use…

Knuckles-Team/servicenow-api · 130 tokens

servicenow-import-attachment-batch

ServiceNow data-ingest, file, and batched-REST surface — push rows through Import Sets (single & bulk), upload/get/delete record attachments, and bundle many REST calls into one batch request via the servicenow-api MCP server. Use when the agent must load external data through a transform-mapped import set, attach or…

Knuckles-Team/servicenow-api · 144 tokens

servicenow-platform-utilities

ServiceNow cross-domain platform helpers — send notification email, render deployed Flow Designer flows to Mermaid and read flow metadata, fetch data-classification and application metadata, list activity subscriptions, and push MetricBase time-series via the servicenow-api MCP server. Use when the agent needs a…

Knuckles-Team/servicenow-api · 156 tokens

servicenow-table-api

Foundational ServiceNow data access — generic Table API CRUD, Aggregate/stats roll-ups, and raw REST escape-hatch via the servicenow-api MCP server. Use when the agent must read, insert, update, patch, delete, count, or aggregate records in ANY ServiceNow table (including scoped app tables with no dedicated API), or…

Knuckles-Team/servicenow-api · 180 tokens

servicenow-telecom-tmf

ServiceNow Telecom (TSM/TSOM) TM Forum Open APIs — drives service qualification (TMF645), product inventory (TMF637), account (TMF666/629), and any other TM Forum Open API (TMF622 product ordering, TMF641 service ordering, TMF642 alarm management) exposed by Store-installed scoped telecom apps. Use when the agent must…

Knuckles-Team/servicenow-api · 202 tokens

servicenow-workflow-studio

Author ServiceNow Flow Designer flows, subflows, and actions as code with the Fluent @servicenow/sdk/automation API (Flow, Subflow, wfa.trigger, wfa.action, wfa.flowLogic, wfa.dataPill), plus how each Fluent construct maps to the Flow Designer UI. Use when the agent must write or explain a flow, subflow, trigger…

Knuckles-Team/servicenow-api · 199 tokens