Borrowing it
Nothing to install: this file belongs to vish288/mcp-gitlab. 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/vish288/mcp-gitlab/main/AGENTS.mdgit clone --depth 1 https://github.com/vish288/mcp-gitlabWrote 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/instructions/vish288/mcp-gitlab/agents-md)<a href="https://agentmods.dev/instructions/vish288/mcp-gitlab/agents-md"><img src="https://agentmods.dev/badge/instructions/vish288/mcp-gitlab/agents-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.
<a href="https://agentmods.dev/instructions/vish288/mcp-gitlab/agents-md"><img src="https://agentmods.dev/badge/instructions/vish288/mcp-gitlab/agents-md.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.05703 | $0.05703 |
| Opus 5.5 | $0.02281 | $0.02281 |
| Sonnet 5.5 | $0.01141 | $0.01141 |
| Haiku 4.5 | $0.00570 | $0.00570 |
Grade A, and why
mcp-gitlab AGENTS.md 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 7d 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.
How it starts
The opening of the file, as written. The whole thing — 274 lines — stays where its author put it; the contents beside it link to each section on GitHub.
mcp-gitlab — Agent Context
MCP server exposing 91 tools, 7 resources, and 6 prompts over the GitLab REST API v4. Covers the full project lifecycle: code, reviews, CI/CD, releases, and issue tracking. Works against GitLab.com and self-hosted instances.
Protocol Support
Supports the MCP 2026-07-28 specification (MCP 2.0) and stays compatible with 2025-11-25
clients. Built on FastMCP 4.x and the MCP Python SDK 2.x. Verified over stdio and
streamable-http.
Transports: stdio (default), streamable-http (recommended for remote), and sse. The
2026-07-28 specification deprecates sse, so the server prints a warning when you use it. The
server uses no roots, sampling, logging, elicitation, or resource subscriptions, so the
2026-07-28 deprecations do not affect it.
Authorization: with --auth oauth (streamable-http only) the server is an MCP 2026-07-28 resource
server and OAuth proxy in front of GitLab (RFC 9728 PRM, RFC 8414 AS metadata, PKCE S256, per-user
GitLab tokens). The auth MUSTs are covered by in-process HTTP tests in tests/unit/test_oauth_http.py,
not by a CI conformance job: the MCP conformance suite has no server-side auth scenarios (auth/*
are client scenarios), so a conformance job cannot prove them.
Architecture
- Entry point:
src/mcp_gitlab/__init__.py— click CLI, loads.envvia python-dotenv, runs the FastMCP server - Client:
src/mcp_gitlab/client.py— async httpx client with all GitLab API methods. Transport (R2): a per-phasehttpx.Timeoutwith the connect phase capped at 10s andAsyncHTTPTransport(retries=2)for connection errors;_sendadds GET-only status retries (502/503/504 with jitter, 429 whenRetry-After≤ 5s, max 2 attempts, writes never retried — kept separate from the refresh-on-401 retry) and splits a timeout (GitLabTimeoutError) from an unreachable host (GitLabConnectionError; aConnectTimeoutcounts as unreachable); an unresolved 429 surfacesretry_afterviaGitLabRateLimitError. Worst-case latency against a hard-down host is roughly2 × (3 × connect-cap + timeout) + jitter(connect cap 10s; the two outer attempts each wrap httpx's three connect tries) - Tools:
src/mcp_gitlab/servers/gitlab.py— all 91 FastMCP tool registrations - Resources:
src/mcp_gitlab/servers/resources.py— 7 MCP resources (4resource://rules/*, 3resource://guides/*), content insrc/mcp_gitlab/resources/*.md - Prompts:
src/mcp_gitlab/servers/prompts.py— 6 MCP prompts (multi-tool workflows) - Helpers:
src/mcp_gitlab/servers/_helpers.py— cached file loader with path-traversal guard, plus GitLab URL parsers. Most tools accept a project ID, a path, or a full GitLab URL forproject_id; MR and pipeline URLs also yield the iid/id - Config:
src/mcp_gitlab/config.py—GitLabConfigdataclass built from env vars;GITLAB_TIMEOUTis validated with a named error, and the CLI validates config beforerun_async(exit 2, one line) for token mode too, not just oauth - Local sign-in:
src/mcp_gitlab/local_auth.py— device and PKCE flows, credentials file, refresh under lock; used when no env token is set - OAuth:
src/mcp_gitlab/oauth.py—GitLabProvider(a fastmcpOAuthProxyin front of GitLab) andGitLabTokenVerifier(validates a GitLab OAuth token viaGET /oauth/token/info). Only used when--auth oauth - Exceptions:
src/mcp_gitlab/exceptions.py—GitLabErrorbase;GitLabApiError,GitLabAuthError,GitLabNotFoundError,GitLabRateLimitError(withretry_after),GitLabTimeoutError,GitLabConnectionError,GitLabWriteDisabledError - Tests:
tests/—unit/test_tools.py(143 tool-level tests via the FastMCP in-memory client), plustest_client.py,test_config.py,test_local_auth.py,test_exceptions.py,test_prompts.py,test_resources.py, andtests/test_links.py. Shared fixtures (config,client,mock_apivia respx) live intests/conftest.py
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.
- 7d ago Changed · +242 tokens per session c7b07c5b7cec
- 8d ago Changed · +19 lines · +413 tokens per session bba6a1cde3a2
- 12d ago Changed · +78 tokens per session ba0646e21b5a
- 13d ago Changed · +12 tokens per session 513a86cee4dd
- 15d ago Changed · +45 tokens per session 99411a0b8fbf
- 16d ago Changed · +26 lines · +664 tokens per session 847156825be6
- 17d ago Changed · +90 tokens per session 23225b2b40d7
- 18d ago Changed · +8 lines · +367 tokens per session e0ef936b547b
- 23d ago Changed · +3 lines · +183 tokens per session d76ee6bef148
- 24d ago First seen · 218 lines · 3,609 tokens per session scan A 77f3023505c2
mcp-gitlab AGENTS.md is an instructions file published in the GitHub repository vish288/mcp-gitlab (6 stars, last pushed 4d ago), licensed MIT. It adds 5,703 tokens to every session, about $0.0228 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-31.
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).
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.
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).
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.
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).
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.