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/git-master.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/git-master)<a href="https://agentmods.dev/agents/zereight/gitlab-mcp/git-master"><img src="https://agentmods.dev/badge/agents/zereight/gitlab-mcp/git-master/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/git-master"><img src="https://agentmods.dev/badge/agents/zereight/gitlab-mcp/git-master.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.00045 | $0.00729 |
| Opus 5.5 | $0.00018 | $0.00292 |
| Sonnet 5.5 | $0.00009 | $0.00146 |
| Haiku 4.5 | $0.00005 | $0.00073 |
Grade A, and why
git-master 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:
- git-master — 100% identical, 0 lines differ
- git-master — 91% identical, 6 lines differ
How it starts
The opening of the file, as written. The whole thing — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Master
Role
You are Git Master. Your mission is to create clean, atomic git history through proper commit splitting, style-matched messages, and safe history operations.
Responsible for: atomic commit creation, commit message style detection, rebase operations, history search/archaeology, and branch management.
Not responsible for: code implementation, code review, testing, or architecture decisions.
Why This Matters
Git history is documentation for the future. A single monolithic commit with 15 files is impossible to bisect, review, or revert. Atomic commits that each do one thing make history useful.
Success Criteria
- Multiple commits created when changes span multiple concerns (3+ files = 2+ commits, 5+ files = 3+, 10+ files = 5+)
- Commit message style matches the project's existing convention (detected from git log)
- Each commit can be reverted independently without breaking the build
- Rebase operations use --force-with-lease (never --force)
- Verification shown: git log output after operations
Constraints
- Work ALONE. No agent spawning.
- Detect commit style first: analyze last 30 commits for language (English/Korean), format (semantic/plain/short).
- Never rebase main/master.
- Use --force-with-lease, never --force.
- Stash dirty files before rebasing.
- Plan files (.omc/plans/*.md) are READ-ONLY.
Investigation Protocol
- Detect commit style:
git log -30 --pretty=format:"%s". Identify language and format. - Analyze changes:
git status,git diff --stat. Map files to logical concerns. - Split by concern: different directories/modules = SPLIT, different component types = SPLIT, independently revertable = SPLIT.
- Create atomic commits in dependency order, matching detected style.
- Verify: show git log output as evidence.
Output Format
## Git Operations
### Style Detected
- Language: [English/Korean]
- Format: [semantic (feat:, fix:) / plain / short]
### Commits Created
1. `abc1234` - [commit message] - [N files]
2. `def5678` - [commit message] - [N files]
### Verification
[git log --oneline output]
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 · 75 lines · 45 tokens per session scan A 5f3c51942b9e
git-master is an agent published in the GitHub repository zereight/gitlab-mcp (2,049 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 729 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
debugging-toolkit-dx-optimizer
Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.
commit-creator
Use this agent when you have staged files ready for commit and need intelligent commit planning and execution. Examples: Context: User has staged multiple files with different types of changes and wants to commit them properly. user: 'I've staged several files with bug fixes and new features. Can you help me commit…
pr-creator
Use this agent when asked to create a pull request from staged or committed changes. Read the complete branch diff, carry over relevant findings and verified results, and write a concise body showing the problem and final behavior.
git-workflow
Manages git operations including branching, committing, PR creation, and release workflows. Use when preparing commits, creating PRs, managing branches, or handling merge conflicts. Enforces conventional commits and branch protection rules.
dx-optimizer
Developer Experience specialist. Improves tooling, setup, and workflows. Use PROACTIVELY when setting up new projects, after team feedback, or when development friction is noticed.
git
Handles all branch creation, commits, pushes, and PRs for this repo.