Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add bendrucker/claude/plugin install gitlabWrote 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/bendrucker/claude/merge-request)<a href="https://agentmods.dev/skills/bendrucker/claude/merge-request"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/merge-request/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/bendrucker/claude/merge-request"><img src="https://agentmods.dev/badge/skills/bendrucker/claude/merge-request.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.00078 | $0.01632 |
| Opus 5.5 | $0.00031 | $0.00653 |
| Sonnet 5.5 | $0.00016 | $0.00326 |
| Haiku 4.5 | $0.00008 | $0.00163 |
Grade A, and why
gitlab:merge-request 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 4d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Merge Requests
Working with GitLab merge requests via glab mr.
Scripts directory (absolute, for invocations from other skills where ${CLAUDE_SKILL_DIR} points elsewhere): !mkdir -p /tmp/claude/gitlab-skill 2>/dev/null; touch "/tmp/claude/gitlab-skill/${CLAUDE_SESSION_ID}" 2>/dev/null; echo "${CLAUDE_SKILL_DIR}/scripts"
Arguments
$0 (optional verb) routes to a section below. With no verb, infer the operation from the request.
create: open an MR. See Patterns.--draftopens it as a draft (glab mr create --draft).merge: merge the MR. See Merging.--autoenables auto-merge (merge.ts --auto-merge).review: review MRs. See Reviews.--role reviewer(default) fetches MRs awaiting your review;--role authortriages threads on MRs you authored.discussions: work MR discussion threads. See Discussions.block: block an MR until another merges. See Blocking.
Flag defaults: --draft off, --auto off, --role reviewer.
Merging
Always use merge.ts to merge. It handles merge trains, auto-merge, and squash, falling back to glab mr merge internally when appropriate.
bun ${CLAUDE_PLUGIN_ROOT}/scripts/merge.ts
bun ${CLAUDE_PLUGIN_ROOT}/scripts/merge.ts --auto-merge
bun ${CLAUDE_PLUGIN_ROOT}/scripts/merge.ts feature-branch --auto-merge --squash
Never call glab mr merge directly. It turns auto-merge on by default whenever a pipeline is running. A bare invocation then queues the MR to merge itself later instead of merging it now, silently breaking a deliberate merge order. merge.ts always sends --auto-merge=<choice> so the default cannot apply.
Inspect Before Merging
--status prints the MR's merge readiness as JSON and exits without touching it: target branch, draft state, detailed_merge_status, head pipeline, and a rebased_on_target ancestry check computed from git rather than the API's stale conflict fields.
bun ${CLAUDE_PLUGIN_ROOT}/scripts/merge.ts --status
bun ${CLAUDE_PLUGIN_ROOT}/scripts/merge.ts feature-branch --status
What ships with it
15 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.
- blocking.md 429 B
- discussions.md 6.2 KB
- merge-trains.md 463 B
- review-state.md 4.8 KB
- review.md 6.1 KB
- scripts/diff.test.ts 5.2 KB runs code
- scripts/diff.ts 4.5 KB runs code
- scripts/discussions.test.ts 8.2 KB runs code
- scripts/discussions.ts 11 KB runs code
- scripts/draft-note.ts 7.7 KB runs code
- scripts/review-queue.test.ts 3.2 KB runs code
- scripts/review-queue.ts 2.8 KB runs code
- scripts/reviewers.test.ts 1.4 KB runs code
- scripts/reviewers.ts 1.1 KB runs code
- stacked-mrs.md 1.9 KB
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.
- 4d ago Changed dbe42fe29709
- 1mo ago Changed · +2 lines e4bb70921e18
- 1mo ago First seen · 120 lines · 78 tokens per session scan A 06020cbd0def
gitlab:merge-request is a skill published in the GitHub repository bendrucker/claude (18 stars, last pushed today), licensed MIT. It adds 78 tokens to every session and 1,632 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-30.
Other skills, from other repositories
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
pr
Comprehensive PR/issue review - analyzes architecture, tests, identifies unrelated changes mixed in, drafts review comment or issue comment. Use when user asks to review a PR, check a PR, look at PR changes, or comment on an issue.
pr-threads-address
Address PR review feedback by systematically working through every unresolved PR review thread on the current branch's PR - analyze each comment, make the requested code changes (with tests where useful), commit, and optionally reply and resolve.
han-release
Cut a Han release: update CHANGELOG.md with the changes since the last release, bump and tag every plugin that changed as {plugin-name}--v{version} so a version-constrained dependency can resolve, and publish a GitHub release crediting every merged pull request and closed issue to the people behind it. Use when…
pr-comment
Post friendly review comments to a GitHub PR — prepare locally, preview, then submit as atomic review. Use when: posting code review comments, giving PR feedback, sending inline suggestions. Not for: reading existing reviews (use load-pr-review), creating PRs (use create-pr), PR status (use pr-summary).
deploy-landed
A deployment verification procedure that checks whether the intended code revision is actually running, its environment settings are present, and the product works. A deployment is the process of putting new software on a server or hosting platform.