gitlab-mcp: Skill for Claude Code

.github/skills/verify/SKILL.md

verify is a skill for Claude Code from kirti12025/gitlab-mcp. It costs 29 tokens per session (222 once invoked), scanned A, a copy of verify, MIT.

A verification workflow that gathers evidence that a code change works before calling it complete.

In plain words
What is it for?
Use it to verify a requested behavior, run the narrowest useful checks, and summarize what passed and what did not.
Why use it?
It replaces assumptions with test, build, type-check, command, or manual-check results and clearly reports anything that failed or remains untested.

Skill for Claude Code

Written for Claude Code: argument-hint 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/skills/verify/SKILL.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 verify

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/kirti12025/gitlab-mcp/verify"><img src="https://agentmods.dev/badge/skills/kirti12025/gitlab-mcp/verify.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 222 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.00029 $0.00222
Opus 5.5 $0.00012 $0.00089
Sonnet 5.5 $0.00006 $0.00044
Haiku 4.5 $0.00003 $0.00022

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

Security

Grade A, and why

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

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 verify — 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/skills/verify/SKILL.md · 37 lines

What it actually says

Verify

Turn vague "it should work" claims into concrete evidence.

Workflow

  1. Identify the exact behavior that must be proven
  2. Prefer existing tests first
  3. If coverage is missing, run narrowest direct verification commands
  4. If direct automation not enough, describe manual validation steps
  5. Report only what was actually verified

Verification Order

  1. Existing tests
  2. Typecheck / build
  3. Narrow direct command checks
  4. Manual or interactive validation

Rules

  • Do not say a change is complete without evidence
  • If a check fails, include the failure clearly
  • If no realistic verification path exists, say so explicitly
  • Prefer concise evidence summaries over noisy logs

Output

  • What was verified
  • Which commands/tests were run
  • What passed
  • What failed or remains unverified
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 · 37 lines · 29 tokens per session scan A a20474e601ba

Subscribe to this mod's changes

verify is a skill published in the GitHub repository kirti12025/gitlab-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 222 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to verify, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

jetson-validate-image

Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.

NVIDIA/skills · 50 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

skill-benchmark

Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.

HoangNguyen0403/agent-skills-standard · 16 tokens