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 grandcamel/GitLab-Assistant-Skills --skill gitlab-mrgit 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-mr)<a href="https://agentmods.dev/skills/grandcamel/gitlab-assistant-skills/gitlab-mr"><img src="https://agentmods.dev/badge/skills/grandcamel/gitlab-assistant-skills/gitlab-mr/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/grandcamel/gitlab-assistant-skills/gitlab-mr"><img src="https://agentmods.dev/badge/skills/grandcamel/gitlab-assistant-skills/gitlab-mr.svg" alt="Reviewed on agentmods" width="80" 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.00073 | $0.02451 |
| Opus 5.5 | $0.00029 | $0.00980 |
| Sonnet 5.5 | $0.00015 | $0.00490 |
| Haiku 4.5 | $0.00007 | $0.00245 |
Grade A, and why
gitlab-mr 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 2mo 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 — 363 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge Request Skill
Merge request operations for GitLab using the glab CLI.
Quick Reference
| Operation | Command | Risk |
|---|---|---|
| List MRs | glab mr list |
- |
| View MR | glab mr view <id> |
- |
| Create MR | glab mr create |
⚠️ |
| Checkout MR | glab mr checkout <id> |
- |
| Approve MR | glab mr approve <id> |
⚠️ |
| Merge MR | glab mr merge <id> |
⚠️⚠️ |
| Update MR | glab mr update <id> |
⚠️ |
| Close MR | glab mr close <id> |
⚠️ |
| Reopen MR | glab mr reopen <id> |
⚠️ |
| Delete MR | glab mr delete <id> |
⚠️⚠️ |
| Rebase MR | glab mr rebase <id> |
⚠️ |
Risk Legend: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger
When to Use This Skill
ALWAYS use when:
- User wants to work with merge requests
- User mentions "MR", "merge request", "pull request", or related terms
- User wants to review, approve, or merge code
NEVER use when:
- User wants bulk operations on 10+ MRs (use gitlab-bulk instead)
- User is only searching/filtering MRs (use gitlab-search instead)
Available Commands
List Merge Requests
glab mr list [options]
Options:
| Flag | Description |
|---|---|
--assignee=@me |
Filter by assignee (use @me for yourself) |
--reviewer=@me |
Filter by reviewer |
--author=<username> |
Filter by author |
--label=<labels> |
Filter by comma-separated labels |
--state=<state> |
Filter by state: opened, closed, merged, all |
--source-branch=<branch> |
Filter by source branch |
--target-branch=<branch> |
Filter by target branch |
-P, --per-page=<n> |
Number of items per page |
Examples:
# List MRs assigned to you
glab mr list --assignee=@me
# List review requests for you
glab mr list --reviewer=@me
# List open MRs with specific label
glab mr list --state=opened --label=bug
# List MRs targeting main branch
glab mr list --target-branch=main
View Merge Request Details
glab mr view <id> [options]
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.
- 2mo ago First seen · 363 lines · 73 tokens per session scan A 40e950c528ff
gitlab-mr is a skill published in the GitHub repository grandcamel/GitLab-Assistant-Skills (4 stars, last pushed 9mo ago), licensed MIT. It adds 73 tokens to every session and 2,451 once invoked, about $0.0003 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
gitlab-ops
Use this skill when performing VCS operations on GitLab or GitHub repositories — creating, updating, or closing issues and MRs, applying label taxonomy, running glab/gh CLI commands, or resolving project paths dynamically. Acts as the single source of truth for CLI command syntax and label conventions; consuming…
gitlab-portfolio
Use when you need a single-pane cross-repo health view across all vault-registered GitLab and GitHub projects. Discovers repos from overview.md frontmatter in /01-projects//, aggregates open issues, MRs, critical labels, and stale signals via parallel glab/gh calls, then writes an idempotent PORTFOLIO.md dashboard.…
session-end
Use this skill when performing a full session close-out: verifies all planned work against the agreed plan, creates issues for gaps, runs quality gates, commits cleanly, mirrors to GitHub, and produces a session summary. Triggered by /close command.
session-start
Use this skill when initializing a session for any project repo. Autonomously analyzes git state, VCS issues, SSOT files, branches, environment, and cross-repo status. Then presents structured findings with recommendations before development wave planning, or an operations contract for explicitly requested…
close
End session with verification, commits, and documentation.
next-issue
Work the next open item on the issue.