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-cicd-devopsgit 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-cicd-devops)<a href="https://agentmods.dev/skills/knuckles-team/servicenow-api/servicenow-cicd-devops"><img src="https://agentmods.dev/badge/skills/knuckles-team/servicenow-api/servicenow-cicd-devops/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-cicd-devops"><img src="https://agentmods.dev/badge/skills/knuckles-team/servicenow-api/servicenow-cicd-devops.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.00185 | $0.01749 |
| Opus 5 | $0.00093 | $0.00874 |
| Sonnet 5 | $0.00037 | $0.00350 |
| Haiku 4.5 | $0.00018 | $0.00175 |
Grade A, and why
servicenow-cicd-devops 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 9d 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 — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ServiceNow CI/CD & DevOps (release engineering)
The operational release surface: promote code between instances, scan it, gate it
through DevOps change control, and prove it with ATF. Six condensed tools cover the
whole pipeline. The full per-action catalog lives in
references/actions-catalog.md — read it just-in-time when you need the exact
parameter names for an action.
When to use
- Install / publish / roll back a scoped app from a source-control app repo.
- Kick off and poll code or instance scans (full / point / combo / suite).
- Gate a deployment through DevOps change control and register artifacts/packages.
- Move configuration between instances with update sets (create → preview → commit).
- Apply remote source-control changes or import a repository.
- Activate or roll back a plugin.
- Run an Automated Test Framework (ATF) test suite.
When NOT to use
- Generic table CRUD / aggregate / raw REST →
servicenow-table-api. - Bulk data ingest, attachments, or bundled REST →
servicenow-import-attachment-batch. - Flow-to-mermaid, email, metricbase, app metadata →
servicenow-platform-utilities. - Authoring an app locally (SDK scaffolding) → the dev-tooling skill
servicenow-sdk-lifecycle; it defers here for the remote deploy/publish/test steps.
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.
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.
- 9d ago First seen · 128 lines · 185 tokens per session scan A b30dd1351f11
servicenow-cicd-devops is a skill published in the GitHub repository Knuckles-Team/servicenow-api (19 stars, last pushed 11d ago), licensed MIT. It adds 185 tokens to every session and 1,749 once invoked, about $0.0009 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
integrating-sast-into-github-actions-pipeline
This skill covers integrating Static Application Security Testing (SAST) tools—CodeQL and Semgrep—into GitHub Actions CI/CD pipelines. It addresses configuring automated code scanning on pull requests and pushes, tuning rules to reduce false positives, uploading SARIF results to GitHub Advanced Security, and…
implementing-infrastructure-as-code-security-scanning
This skill covers implementing automated security scanning for Infrastructure as Code (IaC) templates using tools like Checkov, tfsec, and KICS. It addresses detecting misconfigurations in Terraform, CloudFormation, Kubernetes manifests, and Helm charts before deployment, establishing policy-based governance, and…
integrating-dast-with-owasp-zap-in-pipeline
This skill covers integrating OWASP ZAP (Zed Attack Proxy) for Dynamic Application Security Testing in CI/CD pipelines. It addresses configuring baseline, full, and API scans against running applications, interpreting ZAP findings, tuning scan policies, and establishing DAST quality gates in GitHub Actions and GitLab…
performing-sca-dependency-scanning-with-snyk
This skill covers implementing Software Composition Analysis (SCA) using Snyk to detect vulnerable open-source dependencies in CI/CD pipelines. It addresses scanning package manifests and lockfiles, automated fix pull request generation, license compliance checking, continuous monitoring of deployed applications, and…
scanning-containers-with-trivy-in-cicd
This skill covers integrating Aqua Security's Trivy scanner into CI/CD pipelines for comprehensive container image vulnerability detection. It addresses scanning Docker images for OS package and application dependency CVEs, detecting misconfigurations in Dockerfiles, scanning filesystem and git repositories, and…
securing-github-actions-workflows
This skill covers hardening GitHub Actions workflows against supply chain attacks, credential theft, and privilege escalation. It addresses pinning actions to SHA digests, minimizing GITHUBTOKEN permissions, protecting secrets from exfiltration, preventing script injection in workflow expressions, and implementing…