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 CobolJunkie/gitlab-mcp --skill gitlabgit clone --depth 1 https://github.com/CobolJunkie/gitlab-mcpWrote 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/coboljunkie/gitlab-mcp/gitlab)<a href="https://agentmods.dev/skills/coboljunkie/gitlab-mcp/gitlab"><img src="https://agentmods.dev/badge/skills/coboljunkie/gitlab-mcp/gitlab/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/coboljunkie/gitlab-mcp/gitlab"><img src="https://agentmods.dev/badge/skills/coboljunkie/gitlab-mcp/gitlab.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.00081 | $0.00598 |
| Opus 5.5 | $0.00032 | $0.00239 |
| Sonnet 5.5 | $0.00016 | $0.00120 |
| Haiku 4.5 | $0.00008 | $0.00060 |
Grade A, and why
gitlab 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab
Use the bundled GitLab MCP tools as the primary interface to GitLab. Use local
git for an existing checkout and use glab only as a narrow fallback when it
is installed and the MCP surface does not cover the operation.
Read references/tool-routing.md before selecting tools.
Resolve the project
- Prefer an explicit GitLab project URL, project ID, or
namespace/projectpath from the user. - For a local checkout, inspect
git remote -vand normalize SSH or HTTPS remotes to a GitLab project path. - If the project is still ambiguous, use
search_projects. - Respect
GITLAB_URLfor self-managed or dedicated GitLab instances. Do not assume GitLab.com.
Route specialized workflows
- For unresolved merge-request feedback, use the sibling
gl-address-commentsskill. - For failed merge-request pipelines, use the sibling
gl-fix-ciskill. - For committing, pushing, and opening a draft merge request, use the sibling
gl-publishskill.
General workflow
- Use
get_gitlab_capabilitieswhen availability, version, licensing, permissions, token scope, or instance configuration may explain an outcome. - Read the current GitLab state before proposing or making a change.
- Use the smallest tool that provides the required data.
- Summarize relevant findings, including project, issue, merge request, branch, pipeline, or job identifiers.
- If the user requested a change, make only the scoped change and then read back the resulting state when practical.
- Report links or stable identifiers so the user can verify the result.
Write safety
- Treat tools marked read-only as safe inspection.
- Before a write, confirm the target project and object from the conversation and current state.
- Do not delete branches, files, comments, or other objects unless deletion is explicitly requested.
- Do not merge a merge request, retry or cancel CI, approve a merge request, or resolve review discussions unless the user asked for that outcome.
- Never expose access tokens, job tokens, private variables, or unredacted secrets from logs.
What ships with it
2 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.
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 · 61 lines · 81 tokens per session scan A 75766b339137
gitlab is a skill published in the GitHub repository CobolJunkie/gitlab-mcp (0 stars, last pushed 28d ago), licensed MIT. It adds 81 tokens to every session and 598 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-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
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.