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-assistantnpx skills add grandcamel/GitLab-Assistant-Skills --skill gitlab-assistantgit 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-assistant)<a href="https://agentmods.dev/skills/grandcamel/gitlab-assistant-skills/gitlab-assistant"><img src="https://agentmods.dev/badge/skills/grandcamel/gitlab-assistant-skills/gitlab-assistant.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 | $0.00056 | $0.02721 |
| Opus 5 | $0.00028 | $0.01360 |
| Sonnet 5 | $0.00011 | $0.00544 |
| Haiku 4.5 | $0.00006 | $0.00272 |
Grade A, and why
gitlab-assistant 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 — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab Assistant
Central hub for GitLab automation using the glab CLI. Routes requests to the most appropriate specialized skill.
Quick Reference
| I want to... | Use this skill | Risk |
|---|---|---|
| Work with merge requests | gitlab-mr |
⚠️ |
| Work with issues | gitlab-issue |
⚠️ |
| Check/run CI pipelines | gitlab-ci |
⚠️ |
| Clone/fork/create repos | gitlab-repo |
⚠️ |
| Manage releases | gitlab-release |
⚠️ |
| Manage labels | gitlab-label |
⚠️ |
| Manage milestones | gitlab-milestone |
⚠️ |
| Manage CI/CD variables | gitlab-variable |
⚠️ |
| Manage groups/teams | gitlab-group |
⚠️ |
| Search GitLab | gitlab-search |
- |
| Protect branches | gitlab-protected-branch |
⚠️ |
| Manage webhooks | gitlab-webhook |
⚠️ |
| Repository file operations | gitlab-file |
⚠️ |
| Manage wiki pages | gitlab-wiki |
⚠️ |
| MR/Issue discussions | gitlab-discussion |
⚠️ |
| Project badges | gitlab-badge |
⚠️ |
| Container registry | gitlab-container |
⚠️⚠️ |
| Security vulnerabilities | gitlab-vulnerability |
⚠️ |
Risk Legend: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger
Routing Rules
Rule 1: Explicit Resource Type
Route based on the GitLab resource being worked with:
| Keywords | Route to |
|---|---|
| MR, merge request, pull request, review, approve, merge | gitlab-mr |
| issue, bug, ticket, task, feature request | gitlab-issue |
| CI, CD, pipeline, build, job, deploy, artifacts | gitlab-ci |
| repo, repository, project, clone, fork | gitlab-repo |
| release, tag, version, changelog | gitlab-release |
| label, tag (for issues/MRs) | gitlab-label |
| milestone, sprint, iteration | gitlab-milestone |
| variable, secret, env, CI variable | gitlab-variable |
| group, team, organization, members, namespace | gitlab-group |
| search, find, query (global/group/project) | gitlab-search |
| protect branch, branch protection, access rules | gitlab-protected-branch |
| webhook, hook, notification callback, integration | gitlab-webhook |
| file, blob, content, raw (repository files) | gitlab-file |
| wiki, documentation page | gitlab-wiki |
| discussion, thread, comment, note, reply | gitlab-discussion |
| badge, status badge, coverage badge | gitlab-badge |
| container, registry, docker, image, tag (container) | gitlab-container |
| vulnerability, security, scan, CVE, SAST, DAST | gitlab-vulnerability |
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.
- 5d ago First seen · 281 lines · 56 tokens per session scan A 37eb9696672a
gitlab-assistant is a skill published in the GitHub repository grandcamel/GitLab-Assistant-Skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 56 tokens to every session and 2,721 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.