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/gitlab-api --skill gitlab-vulnerabilitiesgit clone --depth 1 https://github.com/Knuckles-Team/gitlab-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/gitlab-api/gitlab-vulnerabilities)<a href="https://agentmods.dev/skills/knuckles-team/gitlab-api/gitlab-vulnerabilities"><img src="https://agentmods.dev/badge/skills/knuckles-team/gitlab-api/gitlab-vulnerabilities/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/gitlab-api/gitlab-vulnerabilities"><img src="https://agentmods.dev/badge/skills/knuckles-team/gitlab-api/gitlab-vulnerabilities.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 43 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.
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.00120 | $0.01262 |
| Opus 5.5 | $0.00048 | $0.00505 |
| Sonnet 5.5 | $0.00024 | $0.00252 |
| Haiku 4.5 | $0.00012 | $0.00126 |
Grade A, and why
gitlab-vulnerabilities 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 7d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab Vulnerabilities
Domain-typed review of a GitLab project's Dependency List and security vulnerabilities — the GitLab equivalent of GitHub's Dependabot dependency/vulnerability review. Covers dependencies at project scope, vulnerabilities at project and group scope, and a single vulnerability by its global ID.
When to use
- Audit a project's dependencies (the Dependency List) — optionally filtered by package manager.
- Review a project's security vulnerabilities (Ultimate).
- Review a group's security vulnerability findings across its projects (Ultimate).
- Fetch one vulnerability by its global
vulnerability_id.
When NOT to use
- Publishing/reading packages in the package registry →
gitlab-packages. - CI/CD pipeline results and job logs →
gitlab-pipelines. - Issues / epics / milestones →
gitlab-issues. - Branch/commit/tag/project reads →
gitlab-repositories.
Prerequisites & environment
Connect via the mcp-client skill against the gitlab-api MCP server.
| Variable | Required | Notes |
|---|---|---|
GITLAB_URL |
✅ | GitLab instance base URL |
GITLAB_TOKEN |
✅ | Access token with api scope; project/group Reporter+ for security data |
GITLAB_SSL_VERIFY |
optional | TLS verification toggle |
VULNERABILITIESTOOL |
optional | Tool-group toggle (defaults True); set False to disable |
Full env/tag matrix: the mcp-client reference agent-tools/mcp-client/references/gitlab-api.md.
MCP_TOOL_MODE (condensed|verbose|both) selects the condensed vs. one-to-one verbose tools.
The Vulnerabilities and findings endpoints require GitLab Ultimate with security scanning enabled. The Dependency List requires a Dependency Scanning job to have run. Without these the endpoints return empty results or
403/404— that is a licensing/config state, not a tool bug.
Tools & actions
| Condensed tool | Actions |
|---|---|
gitlab_vulnerabilities |
dependencies, get_project, get_group, get |
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.
- 7d ago Changed 3fb9f67e17f7
- 1mo ago First seen · 108 lines · 120 tokens per session scan A c54ed44e229f
gitlab-vulnerabilities is a skill published in the GitHub repository Knuckles-Team/gitlab-api (10 stars, last pushed 5d ago), licensed MIT. It adds 120 tokens to every session and 1,262 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
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…
x-reader
Read source URLs from X/Twitter, articles, YouTube, Bilibili, podcasts, WeChat, Xiaohongshu, Telegram, RSS, and the open web. Use when the user provides a link and wants the original content, evidence, transcript, summary, or source-grounded analysis.
analyzer
Turn source content or a verified transcript into a structured, evidence-grounded analysis with key insights, risks, and action items.
vibeue
Unreal Engine 5 development using the VibeUE Python API. Use when working in Unreal Engine — blueprints, state trees, materials, actors, landscapes, animation, niagara, widgets, sound, foliage, gameplay tags, enhanced input, skeletons, PCG (procedural content generation), and more. VibeUE is an extension of Unreal's…
build-and-compile
Building, compiling, and resolving dependency issues across languages.
mcp-tools-reference
MUST READ before first MCP tool call in a session. Complete Envoy tool catalog with parameters and usage.