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.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/zereight/gitlab-mcp/skill-stocktakenpx skills add zereight/gitlab-mcp --skill skill-stocktakegit 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/skills/zereight/gitlab-mcp/skill-stocktake)<a href="https://agentmods.dev/skills/zereight/gitlab-mcp/skill-stocktake"><img src="https://agentmods.dev/badge/skills/zereight/gitlab-mcp/skill-stocktake.svg" alt="Measured on agentmods" 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.00060 | $0.01074 |
| Opus 5 | $0.00030 | $0.00537 |
| Sonnet 5 | $0.00012 | $0.00215 |
| Haiku 4.5 | $0.00006 | $0.00107 |
Grade A, and why
skill-stocktake 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 6d 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:
- skill-stocktake — 100% identical, 0 lines differ
- skill-stocktake — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill Stocktake
Audit the .github/skills/ and vscode-omg/resources/templates/skills/ directories to produce a quality and coverage report.
When to Use
- Before adding new skills (to avoid duplication)
- After a large change batch (to verify templates are in sync)
- Periodically to prune stale or incomplete skills
Audit Protocol
Step 1: Inventory
# List all skill directories
ls -1d .github/skills/*/
# Count total
ls -1d .github/skills/*/ | wc -l
# Check each has a SKILL.md
for dir in .github/skills/*/; do
[ -f "${dir}SKILL.md" ] || echo "MISSING SKILL.md: $dir"
done
Step 2: Frontmatter Validation (v1.0.5+)
Each SKILL.md MUST have valid frontmatter:
---
name: skill-name # required, kebab-case, matches directory name
description: > # required, multi-line description with trigger keywords
...
argument-hint: "..." # optional, describes argument
---
v1.0.5 breaking changes to check:
- ❌
hint:field → ✅argument-hint: - ❌
allowed-tools:field → ✅ remove (not supported) - Skill name
autopilot→ must beomg-autopilot(naming collision)
Validate with:
# Find skills using old 'hint:' field
grep -rn "^hint:" .github/skills/
# Find skills using unsupported 'allowed-tools:'
grep -rn "^allowed-tools:" .github/skills/
# Check for old 'autopilot' directory
ls .github/skills/ | grep "^autopilot$"
Step 3: Template Sync Check
# Skills in .github but not in templates
diff <(ls .github/skills/) <(ls vscode-omg/resources/templates/skills/)
# Skills in templates but not in .github (orphan templates)
diff <(ls vscode-omg/resources/templates/skills/) <(ls .github/skills/)
Step 4: Quality Checks
For each skill, check:
-
name:matches directory name exactly -
description:includes trigger keywords ("Activate when: X, Y, Z") - Has a clear "When to Use" or "Steps" section
- Has an "Output Format" or "See Also" section
- No broken cross-references to renamed skills (
/autopilot→/omg-autopilot) - File is not empty stub (< 20 lines = likely incomplete)
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.
- 6d ago First seen · 139 lines · 60 tokens per session scan A 93c68d119cbf
skill-stocktake is a skill published in the GitHub repository zereight/gitlab-mcp (1,953 stars, last pushed yesterday), licensed MIT. It adds 60 tokens to every session and 1,074 once invoked, about $0.0003 per session on Opus 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…