servicenow-atlas: Skill for Claude Code

.agents/skills/readme-maintenance/SKILL.md

readme-maintenance is a skill for Claude Code, Codex from sagar-shirwalkar/servicenow-atlas. It costs 70 tokens per session (951 once invoked), scanned A, original, Apache-2.0.

A checklist for keeping a project's README accurate as the code changes. A README is the main guide to a project, and this checklist covers file diagrams, commands, configuration examples, versions, architecture notes, and links.

In plain words
What is it for?
Use it when editing a README, changing project files, modifying command-line options or configuration, updating versions, changing architecture, or changing headings and sections.
Why use it?
It helps catch documentation that still describes old files, commands, settings, versions, or system behavior. This reduces confusion for people using or maintaining the project.

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/readme-maintenance/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 readme-maintenance

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/sagar-shirwalkar/servicenow-atlas/readme-maintenance"><img src="https://agentmods.dev/badge/skills/sagar-shirwalkar/servicenow-atlas/readme-maintenance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 951 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.00070 $0.00951
Opus 5 $0.00035 $0.00476
Sonnet 5 $0.00014 $0.00190
Haiku 4.5 $0.00007 $0.00095

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

Security

Grade A, and why

readme-maintenance 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/readme-maintenance/SKILL.md · 108 lines

How it starts

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

When to use

  • Adding/removing/renaming a file in the project — is the tree diagram still right?
  • Changing a CLI flag, config key, or command signature — are all code blocks updated?
  • Bumping a version — does the "current version" note need updating?
  • Changing architecture (e.g., swapping build strategy) — are all prose claims still true?
  • Adding or removing a section — does the table of contents still match?
  • Editing the README at all — always check for stale claims while you're there.

Rot patterns to catch

1. Stale prose claims

Assertions about how the system works that were true at vN but wrong at vN+1. Search the README for every occurrence of the changed concept.

Common culprits:

  • Build/deploy strategy — "CI does X" after CI was rewritten
  • Default behavior — "the server auto-selects Y" after the default was changed to Z
  • Dependency claims — "requires pandas" after it was removed
  • Status labels[planned] on something now implemented, or vice versa

2. Broken section references

Internal links [§5.3](#53-smoke-test-ci) break when section headings change. After editing any heading, grep the README for the old anchor text and update every cross-reference.

3. Version note rot

Many READMEs have a "current version" callout box. This should be updated on every release — at minimum the version number and a one-line summary of what changed. If you bump the version in pyproject.toml but not the README note, it's wrong.

4. ASCII tree diagram drift

Directory structure diagrams (├── foo.py description) rot silently because they look right at a glance. After any file add/remove/rename:

  • Verify every file in the diagram still exists

  • Verify every file in the project that matters is listed

  • Align descriptions vertically — pick a column position for descriptions and pad every filename to it. Use monospace alignment: the longest filename in the diagram sets the column for its nesting level.

    Bad (misaligned):

    ├── foo.py        Does X
    ├── bar.py                  Does Y
    ├── baz-long-name.py   Does Z
    

Read the full file on GitHub · 108 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 · 108 lines · 70 tokens per session scan A 0beb43df79d2

Subscribe to this mod's changes

readme-maintenance is a skill published in the GitHub repository sagar-shirwalkar/servicenow-atlas (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 70 tokens to every session and 951 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-cicd-devops

ServiceNow release-engineering surface — CI/CD app install/scan/rollback, DevOps change-control & artifact registration, update-set create/preview/commit/back-out, source-control apply/import, plugin activate/rollback, and ATF test-suite runs via the servicenow-api MCP server. Use when the agent must deploy or roll…

Knuckles-Team/servicenow-api · 185 tokens

servicenow-studio-gitlab-app

Wire a ServiceNow scoped app (App Engine Studio / Fluent) to a GitLab repository and drive its promotion two ways — Path A: native Studio source control (servicenowsourcecontrol → importrepository / applyremotesourcecontrolchanges, handing off to servicenowcicd for publish/install), or Path B: GitLab-CI-driven…

Knuckles-Team/servicenow-api · 254 tokens

servicenow-change-management

ITSM change-management operations on the ServiceNow Change API via the servicenow-api MCP server — the full change-request lifecycle: query changes, tasks, schedules, CIs, models and standard-change templates; create/update changes and change-tasks; run risk calculation and conflict checks; approve; and delete. Use…

Knuckles-Team/servicenow-api · 137 tokens

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