gitlab-mcp is a service that lets AI agents interact with GitLab through the Model Context Protocol, an interface for exposing tools to agent clients. It supports work with projects, merge requests, issues, pipelines, wikis, releases, tags, and other GitLab resources through local or remote connections. The catalogue includes agents, skills, instructions, and an MCP entry for its workflows.
Borrowing it
Nothing to install: this file belongs to zereight/gitlab-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/zereight/gitlab-mcp/main/.github/skills/ultrawork/SKILL.mdgit clone --depth 1 https://github.com/zereight/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/zereight/gitlab-mcp/ultrawork)<a href="https://agentmods.dev/skills/zereight/gitlab-mcp/ultrawork"><img src="https://agentmods.dev/badge/skills/zereight/gitlab-mcp/ultrawork/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/zereight/gitlab-mcp/ultrawork"><img src="https://agentmods.dev/badge/skills/zereight/gitlab-mcp/ultrawork.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.00319 |
| Opus 5.5 | $0.00014 | $0.00128 |
| Sonnet 5.5 | $0.00007 | $0.00064 |
| Haiku 4.5 | $0.00003 | $0.00032 |
Grade A, and why
ultrawork 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- ultrawork — 100% identical, 0 lines differ
What it actually says
Ultrawork
Parallel execution engine that runs multiple agents simultaneously for independent tasks. Component mode -- provides parallelism and smart model routing but not persistence or verification loops.
When to Use
- Multiple independent tasks can run simultaneously
- Need to delegate work to multiple agents at once
When NOT to Use
- Need guaranteed completion with verification → use
/ralph(includes ultrawork) - Full autonomous pipeline → use
/omg-autopilot(includes ralph which includes ultrawork) - Only one sequential task → delegate directly to @executor
Relationship
ralph (persistence wrapper)
└── includes: ultrawork (this skill)
omg-autopilot (autonomous execution)
└── includes: ralph
└── includes: ultrawork (this skill)
Steps
- Classify tasks by independence: parallel vs dependent
- Fire independent tasks simultaneously via @executor
- Run dependent tasks sequentially after prerequisites
- Background long operations (builds, installs, tests)
- Verify when all tasks complete (build passes, tests pass)
Execution Policy
- Fire ALL independent tasks simultaneously
- Run builds/tests in background
- Match task complexity to appropriate model routing
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 · 44 lines · 35 tokens per session scan A a99a0e12affe
ultrawork is a skill published in the GitHub repository zereight/gitlab-mcp (2,074 stars, last pushed today), licensed MIT. It adds 35 tokens to every session and 319 once invoked, about $0.0001 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
gitlab-merge-request-review
Review and merge GitLab merge requests via the gitlab-api MCP server — by default the MRs assigned to you or where you are a reviewer, optionally scoped to a project, group, or the whole instance. Read an MR, gate it on a green pipeline (pipeline → jobs → job log), then approve, accept/merge, or set…
gitlab-api-development
Develop, test, gate, and release the GitLab REST and GraphQL connector. Use this skill when changing API mappings, governed MCP tools, authentication, tenant selection, KG ingestion, packaged content, or repository gates.
gitlab-pipelines
CI/CD pipeline review on GitLab via the gitlab-api MCP server — review pipeline results for a project, a group, or the whole instance, drill into the CI jobs of a pipeline, and read a job's log; also trigger a pipeline on a ref. Use when the agent must review CI results across a project/group/organization, check…
gitlab-vulnerabilities
Dependency and security-vulnerability review on GitLab via the gitlab-api MCP server — the GitLab counterpart to GitHub Dependabot. Read a project's Dependency List, review a project's or group's security vulnerabilities/findings, and fetch a single vulnerability by ID. Use when the agent must audit a project's…
gitlab-issues
Issue review and tracking on GitLab via the gitlab-api MCP server — review a project's issues, review issues across a whole group/organization, and read, create, update, or close an issue with the domain-typed tool. Use when the agent must triage a project's issues, see every issue affecting a group, open a new issue…
gitlab-merge-request-create
Open a new GitLab merge request against a project via the gitlab-api MCP server — from a source branch into a target branch, with title, description, assignees, reviewers, labels, and remove-source-branch/squash options. Use when the agent must create/open an MR for a project. Do NOT use to review, approve, or merge…