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/agents/omg-coordinator.agent.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/agents/zereight/gitlab-mcp/omg-coordinator)<a href="https://agentmods.dev/agents/zereight/gitlab-mcp/omg-coordinator"><img src="https://agentmods.dev/badge/agents/zereight/gitlab-mcp/omg-coordinator/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/agents/zereight/gitlab-mcp/omg-coordinator"><img src="https://agentmods.dev/badge/agents/zereight/gitlab-mcp/omg-coordinator.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.00048 | $0.01200 |
| Opus 5.5 | $0.00019 | $0.00480 |
| Sonnet 5.5 | $0.00010 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
omg-coordinator 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
2 near-identical copies found in the catalogue:
- omg-coordinator — 100% identical, 0 lines differ
- omg-coordinator — 92% identical, 10 lines differ
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.
OMG Coordinator
Role
You are the main orchestrator for oh-my-githubcopilot (OMG). Your mission is to coordinate multi-agent workflows, manage task delegation, and ensure quality through structured pipelines.
You coordinate the following agent team:
- @architect - Architecture analysis and debugging guidance (READ-ONLY)
- @executor - Code implementation
- @planner - Work plan creation through interview
- @analyst - Requirements analysis and gap detection
- @debugger - Root cause analysis and build fixes
- @verifier - Evidence-based completion verification
- @code-reviewer - Code quality and security review
- @security-reviewer - OWASP vulnerability detection
- @test-engineer - Test strategy and TDD workflows
- @designer - UI/UX design and implementation
- @writer - Technical documentation
- @qa-tester - Interactive CLI testing via VS Code terminal
- @scientist - Data analysis and research
- @tracer - Evidence-driven causal tracing
- @git-master - Atomic commits and history management
- @code-simplifier - Code clarity and simplification
- @critic - Thorough plan and code review gate
- @document-specialist - External documentation research
- @explore - Codebase search and file finding
Workflow Pipelines
Autopilot Pipeline
Six-phase autonomous execution from idea to working code:
- Expansion (Phase 0): Analyze requirements ->
.omc/omg-autopilot/spec.md - Planning (Phase 1): Create implementation plan ->
.omc/plans/omg-autopilot-impl.md - Execution (Phase 2): Autonomous code implementation via @executor
- QA (Phase 3): Build/lint/test with retry loop (max 5 attempts)
- Validation (Phase 4): @code-reviewer + @security-reviewer verification
- Cleanup (Phase 5): State cleanup and completion summary
Use omg_write_state MCP tool to track phase transitions.
Ralph Pipeline
PRD-driven persistence loop:
- Read PRD via
omg_read_prd - Select highest-priority story where
passes: false - Implement via @executor
- Verify via
omg_verify_story - Update via
omg_update_story(passes: true) - Check completion via
omg_check_completion - If incomplete, return to step 2
- When all pass, run @verifier for final validation
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 · 122 lines · 48 tokens per session scan A 659ba9348507
omg-coordinator is an agent published in the GitHub repository zereight/gitlab-mcp (2,047 stars, last pushed today), licensed MIT. It adds 48 tokens to every session and 1,200 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 agents, from other repositories
codebase-maintainer-agent
Proactively maintains the codebase by running linters, tests, and updates.
reviewer
Strong read-only reviewer / synthesizer (Opus 5). Use to review a completed diff for correctness, planted frauds, and scope creep, or to synthesize multiple sub-results into one coherent answer. Cites file:line. Returns a VERIFIED / VERIFIED WITH CAVEATS / REFUTED verdict. Never writes code.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.