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/ultraqa/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/ultraqa)<a href="https://agentmods.dev/skills/zereight/gitlab-mcp/ultraqa"><img src="https://agentmods.dev/badge/skills/zereight/gitlab-mcp/ultraqa/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/ultraqa"><img src="https://agentmods.dev/badge/skills/zereight/gitlab-mcp/ultraqa.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.00038 | $0.00427 |
| Opus 5.5 | $0.00015 | $0.00171 |
| Sonnet 5.5 | $0.00008 | $0.00085 |
| Haiku 4.5 | $0.00004 | $0.00043 |
Grade A, and why
ultraqa 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 1mo 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:
- ultraqa — 100% identical, 0 lines differ
What it actually says
UltraQA
Autonomous QA cycling workflow that runs until your quality goal is met.
Cycle: run checks → diagnose failures → fix → repeat
Goal Types
| Flag | What to Check |
|---|---|
--tests |
All test suites pass |
--build |
Build succeeds with exit 0 |
--lint |
No lint errors |
--typecheck |
No TypeScript errors |
--interactive |
Interactive CLI/service testing via @qa-tester |
Cycle Workflow (Max 5)
- RUN QA: Execute verification based on goal type
- CHECK RESULT: Pass → exit success. Fail → continue
- DIAGNOSE: @architect analyzes failure, provides root cause
- FIX: @executor applies architect's recommendations
- REPEAT: Go back to step 1
Exit Conditions
- Goal Met: "ULTRAQA COMPLETE: Goal met after N cycles"
- Cycle 5 Reached: Exit with diagnosis
- Same Failure 3x: Exit early with root cause
- Environment Error: Exit with error details
State Tracking
Track in .omc/ultraqa-state.json. Clean up state files on completion.
Output
[ULTRAQA Cycle 1/5] Running tests...
[ULTRAQA Cycle 1/5] FAILED - 3 tests failing
[ULTRAQA Cycle 1/5] Diagnosing...
[ULTRAQA Cycle 2/5] PASSED - All 47 tests pass
[ULTRAQA COMPLETE] Goal met after 2 cycles
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.
- 1mo ago First seen · 50 lines · 38 tokens per session scan A 1cae78ce5f95
ultraqa is a skill published in the GitHub repository zereight/gitlab-mcp (2,049 stars, last pushed today), licensed MIT. It adds 38 tokens to every session and 427 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-30.
Other skills, from other repositories
browser-qa
Use when you need lightweight browser QA for a web page, local HTML file, or app: inspect console errors, broken assets, keyboard/focus behavior, viewport readability, and publish evidence-backed findings JSON through a local HTML report viewer.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
writing-livekit-scenarios
Creates and maintains the scenarios a LiveKit agent simulation runs, and wires the agent to consume them. Use when the user asks "what should I test", "generate simulation scenarios", "write scenarios for my agent", "add a scenario for X", "organize my scenario files", "my simulations are flaky", "the scenario hits my…
running-livekit-simulations
Runs LiveKit agent simulations and acts on the results. Use when the user says "run my simulations", "regression test my agent before deploying", "run the scenarios", "use lk agent simulate", "did my agent pass", "why did this scenario fail", "run simulations in CI", "test the audio pipeline", "check turn-taking and…
designing-tests
Designs and implements testing strategies for any codebase. Use when adding tests, improving coverage, setting up testing infrastructure, debugging test failures, or when asked about unit tests, integration tests, or E2E testing.