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 gl-publishgit 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/gl-publish)<a href="https://agentmods.dev/skills/coboljunkie/gitlab-mcp/gl-publish"><img src="https://agentmods.dev/badge/skills/coboljunkie/gitlab-mcp/gl-publish/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/gl-publish"><img src="https://agentmods.dev/badge/skills/coboljunkie/gitlab-mcp/gl-publish.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.00062 | $0.00450 |
| Opus 5.5 | $0.00025 | $0.00180 |
| Sonnet 5.5 | $0.00012 | $0.00090 |
| Haiku 4.5 | $0.00006 | $0.00045 |
Grade A, and why
gl-publish 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.
What it actually says
Publish Changes to GitLab
Use local git for checkout state, branches, staging, commits, and pushes. Use
the bundled GitLab MCP tools for project resolution and merge-request creation.
Use glab only as a fallback when it is installed and the MCP operation is
unavailable.
Workflow
- Inspect
git status --short, the current branch, the configured remotes, and the full intended diff. - Confirm that the changed files match the user's requested scope. Preserve unrelated work and do not stage it.
- If a new branch is needed, follow the repository's documented branch naming
convention when one exists; otherwise use
gitlab/<short-description>. - Run focused tests or checks appropriate to the change.
- Stage only the intended files and review the staged diff.
- Create one clear commit unless the user requested a different history.
- Push the branch to the resolved GitLab remote.
- Use
create_merge_requestto open a draft merge request with:- a concise title;
- a summary of the change;
- verification performed;
- known limitations or follow-ups.
- Read back the merge request and return its URL.
Guardrails
- Do not include unrelated, generated, credential, or secret files.
- Do not rewrite history, force-push, delete branches, merge, or mark the merge request ready unless explicitly requested.
- Do not claim success until the push and merge-request creation both succeed.
- If tests fail, report the failure and stop before publishing unless the user explicitly directs otherwise.
- If the current branch already has unrelated commits, pause before building a merge request on top of them.
Output
Return the branch, commit, tests, and draft merge-request URL. Clearly identify anything not published.
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.
- 2mo ago First seen · 47 lines · 62 tokens per session scan A 98a42e0b3350
gl-publish is a skill published in the GitHub repository CobolJunkie/gitlab-mcp (0 stars, last pushed 28d ago), licensed MIT. It adds 62 tokens to every session and 450 once invoked, about $0.0002 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
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…
spinout
Use when extracting a project into its own repo — a venture spinout (e.g. a product leaving its incubator repo) or a sanitized content-snapshot fork. Guided 5-step runbook: target sphere + path, confidentiality/sanitize check, copy + fresh git init, SNAPSHOT-FREEZE marker in the source repo, remotes + registration.…
close
End session with verification, commits, and documentation.
next-issue
Work the next open item on the issue.
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for Prisma 8. Use when the user wants to create a pull request, open a PR, or submit changes for review.