gitlab-mcp: Agent for Claude Code

.github/agents/git-master.agent.md

git-master is an agent for Claude Code from kirti12025/gitlab-mcp. It costs 45 tokens per session (729 once invoked), scanned A, a copy of git-master, MIT.

A Git specialist for organizing commits, branches, rebases, and project history. It studies the repository's existing commit style before changing history.

In plain words
What is it for?
Use it to create separate commits for separate concerns, match existing commit-message conventions, rebase branches, search past changes, and manage branch history.
Why use it?
It helps prevent large, mixed-purpose commits and unsafe history changes that are difficult to review, undo, or investigate later.

Agent for Claude Code

Written for Claude Code: user-invocable in frontmatter. Also seen: model in frontmatter.

This is kirti12025/gitlab-mcp's own configuration. It tells Claude Code how to work on gitlab-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything gitlab-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to kirti12025/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.

Copy the file
curl -O https://raw.githubusercontent.com/kirti12025/gitlab-mcp/custom-tool-pipeline-summary/.github/agents/git-master.agent.md
Clone the repo
git clone --depth 1 https://github.com/kirti12025/gitlab-mcp

Made for: Claude Code.

Wrote 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.

agentmods badge for git-master

README.md
[![agentmods](https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/git-master/github.svg)](https://agentmods.dev/agents/kirti12025/gitlab-mcp/git-master)
Your own site
<a href="https://agentmods.dev/agents/kirti12025/gitlab-mcp/git-master"><img src="https://agentmods.dev/badge/agents/kirti12025/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.

agentmods 80×15 button for git-master

Your own site · 80×15
<a href="https://agentmods.dev/agents/kirti12025/gitlab-mcp/git-master"><img src="https://agentmods.dev/badge/agents/kirti12025/gitlab-mcp/git-master.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 45 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 729 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce 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

Measured 1mo ago against content hash 5f3c51942b9e, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

Origin

This is a copy

100% identical to git-master — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.github/agents/git-master.agent.md · 75 lines

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

  1. Detect commit style: git log -30 --pretty=format:"%s". Identify language and format.
  2. Analyze changes: git status, git diff --stat. Map files to logical concerns.
  3. Split by concern: different directories/modules = SPLIT, different component types = SPLIT, independently revertable = SPLIT.
  4. Create atomic commits in dependency order, matching detected style.
  5. 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]

Read the full file on GitHub · 75 lines

Changes

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.

  1. 1mo ago First seen · 75 lines · 45 tokens per session scan A 5f3c51942b9e

Subscribe to this mod's changes

git-master is an agent published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 2mo ago), 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. It is 100% identical to git-master, differing in 0 lines, and is treated as a copy.