gitlab-api

gitlab-api is a skill for Claude Code, Codex from pantheon-org/tekhne. It costs 86 tokens per session (1,204 once invoked), scanned A, original, MIT.

A GitLab integration for retrieving merge request details, comments, and review discussions. A merge request is GitLab’s place for proposing and reviewing code changes.

In plain words
What is it for?
Use it to collect review comments, filter unresolved issues, inspect inline feedback, and create merge request activity reports.
Why use it?
It saves you from manually searching GitLab for reviewer feedback and unresolved discussion threads.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to collect review comments, filter unresolved issues, inspect inline feedback, and create merge request activity reports.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pantheon-org/tekhne/gitlab-api
Install

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.

Any agent
npx skills add pantheon-org/tekhne --skill gitlab-api
Clone the repo
git clone --depth 1 https://github.com/pantheon-org/tekhne

Made for: Claude Code, Codex.

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-api

README.md
[![agentmods](https://agentmods.dev/badge/skills/pantheon-org/tekhne/gitlab-api.svg)](https://agentmods.dev/skills/pantheon-org/tekhne/gitlab-api)
Your own site
<a href="https://agentmods.dev/skills/pantheon-org/tekhne/gitlab-api"><img src="https://agentmods.dev/badge/skills/pantheon-org/tekhne/gitlab-api.svg" alt="Measured on agentmods" height="20"></a>
Per session 86 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,204 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Privilege Escalation · line 94
    Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.
    Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
How audits are shown
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.00086 $0.01204
Opus 5 $0.00043 $0.00602
Sonnet 5 $0.00017 $0.00241
Haiku 4.5 $0.00009 $0.00120

Measured 5d ago against content hash 2ff8804ed304, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

gitlab-api scanned grade A with 1 finding 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 5d ago.

The scan reads SKILL.md. This mod also ships 1 executable file (scripts/get_mr_comments.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

Makes network callslowCapability

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

- Requires: `curl`, `jq`
skills/specialized/gitlab-api/SKILL.md · 127 lines

How it starts

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

GitLab API Integration

Retrieve and analyze GitLab merge request comments and metadata using authenticated API calls.

Prerequisites

  • Set GITLAB_TOKEN or GITLAB_PAT with read_api scope
  • Requires: curl, jq

Available Scripts

get_mr_comments.sh

Fetches all comments from a GitLab merge request.

Location: .agents/skills/gitlab-api/scripts/get_mr_comments.sh

Usage:

.agents/skills/gitlab-api/scripts/get_mr_comments.sh <merge_request_url>

Example:

# Prerequisites assumed: GITLAB_TOKEN with read_api scope
.agents/skills/gitlab-api/scripts/get_mr_comments.sh "https://gitlab.com/your-group/your-project/-/merge_requests/123"

Output Format:

---
Author: Name (@username)
Date: ISO8601 timestamp (UTC)
Type: DiffNote|comment
System: true|false

Comment body text
  • System: true — automated/system-generated message; System: false — human comment
  • Type: DiffNote — inline code review comment; Type: comment — general MR comment
  • Timestamps are UTC in ISO8601 format

Exit Codes:

  • 0: Success
  • 1: Invalid URL format, missing token, or API error

When to Examine Script Internals:

Read script source when debugging unexpected output, extending for custom metadata, or understanding URL encoding. For basic usage, the examples above suffice.

Script location: .agents/skills/gitlab-api/scripts/get_mr_comments.sh (~80 lines)

Common Workflows

Generate MR Review Summary

  1. Fetch and validate comments:
    output=$(.agents/skills/gitlab-api/scripts/get_mr_comments.sh "$MR_URL")
    echo "$output" | grep -q "Author:" || { echo "Invalid response — check token and URL"; exit 1; }
    
  2. Filter by System: false to exclude automated messages
  3. Group by author, extract action items and feedback themes
  4. Generate summary report

Track Review Progress

  1. Fetch and validate comments:
    output=$(.agents/skills/gitlab-api/scripts/get_mr_comments.sh "$MR_URL")
    [ -n "$output" ] && echo "$output" | grep -q "Date:" || { echo "Empty or malformed response — check credentials"; exit 1; }
    
  2. Compare timestamps to identify recent activity
  3. Flag unresolved DiffNotes and report on response times

Read the full file on GitHub · 127 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. 5d ago First seen · 127 lines · 86 tokens per session scan A 2ff8804ed304

Subscribe to this mod's changes

gitlab-api is a skill published in the GitHub repository pantheon-org/tekhne (10 stars, last pushed today), licensed MIT. It adds 86 tokens to every session and 1,204 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories

git-workflow

Git best practices, branching strategies, commit conventions, and code review patterns.

cosmicstack-labs/mercury-agent-skills · 18 tokens

implement-suggestion

Implements review-comment suggestions across one or more PRs. Multi-PR mode (default when $ARGUMENTS contains PR URLs; empty $ARGUMENTS auto-detects the active PR) per PR: resolves a worktree, fetches every actionable comment from both human teammates AND AI code-review bots (claude[bot], coderabbitai[bot], …)…

mthines/agent-skills · 314 tokens

azure-repos

Expert knowledge for Azure Repos development including troubleshooting, best practices, decision making, architecture & design patterns, limits & quotas, security, configuration, and integrations & coding patterns. Use when managing Git/TFVC repos, branch/PR policies, CLI/IDE integrations, CodeQL/scanning, or…

MicrosoftDocs/Agent-Skills · 115 tokens

pr-review

One-shot read-only review of a GitHub PR — dispatches the pr-reviewer agent and reports its verdict and findings without touching your code. The short entry point for "review this PR" when you do not want an apply-and-converge loop. Also writes maintainer relevance rules via /pr-review remember . Invoke with…

mthines/agent-skills · 78 tokens

mx-pr

Draft a pull request from the feature spec and git log, run an autonomous commit-history cleanup (content check), then publish to GitHub or GitLab (Bitbucket experimental) — or hand off. Use when a feature branch is ready for PR, standalone or from mx-flow. Usage: /mx-pr [name].

maxence2997/mx-harness · 67 tokens

mx-commit

Commit all pending changes as one commit per logical concern, following the project's message convention (type prefix, 50-char subject, English). Use when the working tree may hold several changes or the convention must be enforced; a single trivial change can use plain git commit. Usage: /mx-commit [--auto].

maxence2997/mx-harness · 67 tokens