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 agentmods add skills/grandcamel/gitlab-assistant-skills/gitlab-vulnerabilitynpx skills add grandcamel/GitLab-Assistant-Skills --skill gitlab-vulnerabilitygit clone --depth 1 https://github.com/grandcamel/GitLab-Assistant-SkillsWrote 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/grandcamel/gitlab-assistant-skills/gitlab-vulnerability)<a href="https://agentmods.dev/skills/grandcamel/gitlab-assistant-skills/gitlab-vulnerability"><img src="https://agentmods.dev/badge/skills/grandcamel/gitlab-assistant-skills/gitlab-vulnerability.svg" alt="Measured on agentmods" height="20"></a>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.00052 | $0.02617 |
| Opus 5 | $0.00026 | $0.01308 |
| Sonnet 5 | $0.00010 | $0.00523 |
| Haiku 4.5 | $0.00005 | $0.00262 |
Grade A, and why
gitlab-vulnerability 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 5d 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 — 324 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vulnerability Skill
Security vulnerability management for GitLab using glab api raw endpoint calls.
Quick Reference
| Operation | Command Pattern | Risk |
|---|---|---|
| List vulnerabilities | glab api projects/:id/vulnerabilities |
- |
| Get vulnerability | glab api projects/:id/vulnerabilities/:vuln_id |
- |
| Confirm vulnerability | glab api projects/:id/vulnerabilities/:vuln_id/confirm -X POST |
⚠️ |
| Dismiss vulnerability | glab api projects/:id/vulnerabilities/:vuln_id/dismiss -X POST -f ... |
⚠️ |
| Resolve vulnerability | glab api projects/:id/vulnerabilities/:vuln_id/resolve -X POST |
⚠️ |
| Revert to detected | glab api projects/:id/vulnerabilities/:vuln_id/revert -X POST |
⚠️ |
| List findings | glab api projects/:id/vulnerability_findings |
- |
Risk Legend: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger
When to Use This Skill
ALWAYS use when:
- User mentions "vulnerability", "security issue", "CVE"
- User wants to view security scan results
- User mentions "SAST", "DAST", "dependency scanning", "container scanning"
- User wants to dismiss or resolve security findings
- User asks about security dashboard
NEVER use when:
- User wants to run security scans (use gitlab-ci)
- User wants to configure security settings (use project settings)
- User wants general issue tracking (use gitlab-issue)
API Prerequisites
Required Token Scopes: read_api or api
Permissions:
- Read vulnerabilities: Developer+
- Manage vulnerabilities: Developer+
GitLab Tier: Ultimate required for full vulnerability management features
Vulnerability States
| State | Description |
|---|---|
detected |
New, unreviewed vulnerability |
confirmed |
Verified as real vulnerability |
dismissed |
Marked as false positive or won't fix |
resolved |
Fixed and no longer present |
Severity Levels
| Severity | Description |
|---|---|
critical |
Highest severity, immediate action needed |
high |
Significant risk |
medium |
Moderate risk |
low |
Minor risk |
info |
Informational finding |
unknown |
Severity not determined |
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.
- 5d ago First seen · 324 lines · 52 tokens per session scan A f01a5ace96cb
gitlab-vulnerability is a skill published in the GitHub repository grandcamel/GitLab-Assistant-Skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 52 tokens to every session and 2,617 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.
Other skills, from other repositories
code-gauntlet
Prefer this skill for code review requests — it runs a multi-agent pipeline with blind challenge verification for high-confidence results. Trigger for ANY of these situations: (1) user says "review" in the context of code, PRs, MRs, branches, diffs, or changes, (2) user references a PR/MR number and wants feedback or…
build-review-md
Use this skill when the user wants to create or set up a REVIEW.md configuration file for their repository. Trigger for ANY of these: (1) user says "create REVIEW.md", "set up REVIEW.md", or "configure review rules", (2) code-gauntlet Phase 2d detects no REVIEW.md and suggests creating one, (3) user wants to customize…
asana-sweep
Scheduled sweep of incomplete Asana tasks assigned to you — triage into auto/ask/skip, dedupe against existing work, then call asana-to-harness to open GitLab issues that trigger an AI coding harness. Built for headless scheduled runs (claude -p); also runs interactively, with --dry-run support.
asana-to-harness
Turn one Asana task into an implementation plan for an AI coding harness, open a GitLab issue with the plan as its description, and leave a trigger comment (e.g. @claude). Used standalone ("turn this Asana task into a harness issue") or invoked by the asana-sweep skill.
create-site
Creates a new Power Pages code site (SPA) using React, Angular, Vue, or Astro. Guides through the full process from initial concept to deployed site: requirements discovery, scaffolding, component planning, design, implementation, validation, and deployment. Use when the user wants to create, build, or scaffold a new…
review
5-pass structured code review — correctness, security, performance, readability, consistency.