gitlab-mcp: Instructions file for Claude Code

CLAUDE.md

gitlab-mcp CLAUDE.md is an instructions file for Claude Code from wadew/gitlab-mcp. It costs 2,635 tokens per session, scanned C, original, MIT.

A set of development instructions for a GitLab MCP server. It requires test-driven development, meaning tests are written before the code, along with coverage, documentation, and session-management checks.

In plain words
What is it for?
Use it to guide GitLab MCP server changes through failing tests, passing tests, code-coverage checks, phase gates, documentation, and handoffs between work sessions.
Why use it?
It gives development work a fixed quality process and prevents a project from advancing while tests or required records are incomplete.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is wadew/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 wadew/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/wadew/gitlab-mcp/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/wadew/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 gitlab-mcp CLAUDE.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/wadew/gitlab-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/wadew/gitlab-mcp/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,635 This file is loaded in full into every session.
When invoked 2,635 The same file — it is already loaded in full.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.02635 $0.02635
Opus 5.5 $0.01054 $0.01054
Sonnet 5.5 $0.00527 $0.00527
Haiku 4.5 $0.00264 $0.00264

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

Security

Grade C, and why

gitlab-mcp CLAUDE.md scanned grade C with 2 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

curl -LsSf https://astral.sh/uv/install.sh | sh

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -LsSf https://astral.sh/uv/install.sh | sh
CLAUDE.md · 376 lines

How it starts

The opening of the file, as written. The whole thing — 376 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Claude Code Development Guide - GitLab MCP Server

Ground Rules

Test-Driven Development (TDD) - MANDATORY

ALWAYS write tests first. Watch them fail. Then build code to pass them.

  1. Red: Write a failing test that defines desired behavior
  2. Green: Write minimal code to make the test pass
  3. Refactor: Improve code while keeping tests green

No exceptions. No shortcuts. No "I'll add tests later."

Code Coverage Requirements

  • Minimum: 80% code coverage per phase
  • Target: 100% test pass rate
  • Gate: Cannot proceed to next phase without meeting both criteria

Phase Gate Criteria

Before moving to next phase, ALL must be true:

  • ✅ All phase tests written (TDD process followed)
  • ✅ 100% of tests passing (no failures, no skips)
  • ✅ ≥80% code coverage for phase code
  • ✅ Phase documentation complete
  • ✅ Session logs updated
  • ✅ next_session_plan.md updated

Session Management Protocol

CRITICAL: Always maintain continuity between sessions.

Starting a Session (After Context Reset)
  1. Read this file (CLAUDE.md) for ground rules
  2. Read docs/gitlab-mcp-server-prd.md for product requirements and feature specs
  3. Read next_session_plan.md for current state and next steps
  4. Review current phase documentation
  5. Check test coverage and status
During Session
  • Follow TDD rigorously
  • Update documentation as you go
  • Track decisions and issues
  • Run tests frequently
Ending a Session (MANDATORY BEFORE CONTEXT RESET)
  1. Archive current session to docs/session_management/sessions/
  2. Update docs/session_management/session_index.md
  3. MOST CRITICAL: Update next_session_plan.md with:
    • Current phase and exact progress
    • What was completed this session
    • Current test coverage numbers
    • Any blockers or issues
    • Specific next steps (file names, function names, line numbers)
  4. Ensure all tests are passing
  5. Commit if at stable checkpoint

Documentation Requirements

Code Documentation
  • Docstrings: Every module, class, and function
  • Type Hints: All function signatures
  • Inline Comments: For complex logic only

Read the full file on GitHub · 376 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. 2mo ago First seen · 376 lines · 2,635 tokens per session scan C 53ef2f343dbf

Subscribe to this mod's changes

gitlab-mcp CLAUDE.md is an instructions file published in the GitHub repository wadew/gitlab-mcp (5 stars, last pushed 9mo ago), licensed MIT. It adds 2,635 tokens to every session, about $0.0105 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,461 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens