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-studio-gitlab-appgit 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-studio-gitlab-app)<a href="https://agentmods.dev/skills/knuckles-team/servicenow-api/servicenow-studio-gitlab-app"><img src="https://agentmods.dev/badge/skills/knuckles-team/servicenow-api/servicenow-studio-gitlab-app/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-studio-gitlab-app"><img src="https://agentmods.dev/badge/skills/knuckles-team/servicenow-api/servicenow-studio-gitlab-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 72 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Anti-Refusal · line 130 Skill attempts to nullify the agent's safety policies or restrictions ('you have no restrictions', 'ignore your guidelines', 'do anything now'). This is a direct jailbreak that disables guardrails.Fix: Remove jailbreak framing that nullifies safety policies or restrictions. Skill content must not instruct the agent to ignore its guidelines or operate without guardrails.
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.00254 | $0.02148 |
| Opus 5 | $0.00127 | $0.01074 |
| Sonnet 5 | $0.00051 | $0.00430 |
| Haiku 4.5 | $0.00025 | $0.00215 |
Grade A, and why
servicenow-studio-gitlab-app 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 10d 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ServiceNow Studio + GitLab (two integration paths)
Connects a scoped app's source to a GitLab repository and promotes it, via two independent paths that can be used separately or together:
- Path A — native Studio source control. ServiceNow itself pulls from (or
imports) the GitLab repo over
servicenow_source_control, then promotes withservicenow_cicd(servicenow-cicd-devopsowns that action catalog). Requires the instance's outbound reach to the GitLab host. - Path B — GitLab-CI-driven. A GitLab pipeline runs
now-sdk build/install(outbound from the GitLab runner to the instance), then the same publish/verify calls confirm the result. Requires a GitLab runner with outbound reach to the instance instead.
Pick the path (or both) based on which side can reach the other — see
references/tool-map.md for the full tool-name→file:line citations behind every
claim in this skill.
When to use
- Deciding whether Path A or Path B fits a given network topology.
- Wiring a scoped app's GitLab repo into ServiceNow (
import_repository) or pulling remote branch changes into an existing app (apply_remote_source_control_changes). - Authoring or debugging the
.gitlab-ci.ymlthat builds/deploys/promotes/verifies a scoped app through GitLab CI (Path B). - Diagnosing why a Path-A or Path-B promotion didn't reach the instance (perimeter, credential, or runner gaps).
When NOT to use
- The app's metadata shape (tables, ACLs, menus,
now.config.json) →servicenow-app-engine. - The
now-sdkCLI lifecycle itself (init/auth/build/deploy/ATF, run locally or in a pipeline step) →servicenow-sdk-lifecycle. - Flow Designer flows/subflows/actions →
servicenow-workflow-studio. - The full CI/CD & DevOps action catalog (
servicenow_cicd/servicenow_devops/servicenow_update_sets/servicenow_plugins/servicenow_testingparameter reference) once a pipeline already exists →servicenow-cicd-devops. - GitLab-side pipeline authoring/debugging unrelated to a ServiceNow target →
gitlab-api's own
gitlab-pipelinesskill.
What ships with it
4 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.
- 10d ago First seen · 143 lines · 254 tokens per session scan A c42f3e4e989e
servicenow-studio-gitlab-app is a skill published in the GitHub repository Knuckles-Team/servicenow-api (19 stars, last pushed 12d ago), licensed MIT. It adds 254 tokens to every session and 2,148 once invoked, about $0.0013 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
gitlab-merge-request-review
Review and merge GitLab merge requests via the gitlab-api MCP server — by default the MRs assigned to you or where you are a reviewer, optionally scoped to a project, group, or the whole instance. Read an MR, gate it on a green pipeline (pipeline → jobs → job log), then approve, accept/merge, or set…
gitlab-merge-request-create
Open a new GitLab merge request against a project via the gitlab-api MCP server — from a source branch into a target branch, with title, description, assignees, reviewers, labels, and remove-source-branch/squash options. Use when the agent must create/open an MR for a project. Do NOT use to review, approve, or merge…
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
release-changelog-harness
Chooses ecosystem-native release and changelog tooling (Changesets, Melos, release-plz) plus binary distribution (GitHub Release tarballs, install.sh) when the product is an executable. Use for release CI, install.sh, versioning, CHANGELOGs, shipping MCP/CLI without clone, or meta repos that only ship skills via npx…
polish-docs-meta
Finalize documentation and project metadata for a ship-ready release. Use after implementation is complete, tests pass, and devcheck is clean. Safe to run at any stage — each step checks current state and only acts on what still needs work.
github-via-nyxid
Operate a user's GitHub account through NyxID's credential-brokering proxy (service slug api-github) — read and write repositories, files, issues, pull requests, commits, branches, Actions, gists and anything else the GitHub REST API exposes, all on the user's behalf and without ever handling a raw token. NyxID…