gitlab-automation

gitlab-automation is a skill for Claude Code from ratnesh-maurya/cursor-claude-personas. It costs 41 tokens per session (3,548 once invoked), scanned A, original, MIT.

A set of workflows for managing GitLab projects, issues, merge requests, pipelines, branches, and users through connected tools.

In plain words
What is it for?
Use it to search or manage GitLab issues, create or update merge requests, inspect pipelines, manage branches, or perform supported project and user operations.
Why use it?
It provides a defined process for finding the right project, checking the GitLab connection, and carrying out project-management tasks with current tool details.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to search or manage GitLab issues, create or update merge requests, inspect pipelines, manage branches, or perform supported project and user operations.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ratnesh-maurya/cursor-claude-personas/gitlab-automation
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 ratnesh-maurya/cursor-claude-personas --skill gitlab-automation
Clone the repo
git clone --depth 1 https://github.com/ratnesh-maurya/cursor-claude-personas

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

README.md
[![agentmods](https://agentmods.dev/badge/skills/ratnesh-maurya/cursor-claude-personas/gitlab-automation/github.svg)](https://agentmods.dev/skills/ratnesh-maurya/cursor-claude-personas/gitlab-automation)
Your own site
<a href="https://agentmods.dev/skills/ratnesh-maurya/cursor-claude-personas/gitlab-automation"><img src="https://agentmods.dev/badge/skills/ratnesh-maurya/cursor-claude-personas/gitlab-automation/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-automation

Your own site · 80×15
<a href="https://agentmods.dev/skills/ratnesh-maurya/cursor-claude-personas/gitlab-automation"><img src="https://agentmods.dev/badge/skills/ratnesh-maurya/cursor-claude-personas/gitlab-automation.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 41 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,548 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 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.00041 $0.03548
Opus 5 $0.00020 $0.01774
Sonnet 5 $0.00008 $0.00710
Haiku 4.5 $0.00004 $0.00355

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

Security

Grade A, and why

gitlab-automation 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 11d 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

Copies of this mod

1 near-identical copy found in the catalogue:

.claude/skills/gitlab-automation/SKILL.md · 259 lines

How it starts

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

GitLab Automation via Rube MCP

Automate GitLab operations including project management, issue tracking, merge request workflows, CI/CD pipeline monitoring, branch management, and user administration through Composio's GitLab toolkit.

Prerequisites

  • Rube MCP must be connected (RUBE_SEARCH_TOOLS available)
  • Active GitLab connection via RUBE_MANAGE_CONNECTIONS with toolkit gitlab
  • Always call RUBE_SEARCH_TOOLS first to get current tool schemas

Setup

Get Rube MCP: Add https://rube.app/mcp as an MCP server in your client configuration. No API keys needed — just add the endpoint and it works.

  1. Verify Rube MCP is available by confirming RUBE_SEARCH_TOOLS responds
  2. Call RUBE_MANAGE_CONNECTIONS with toolkit gitlab
  3. If connection is not ACTIVE, follow the returned auth link to complete GitLab OAuth
  4. Confirm connection status shows ACTIVE before running any workflows

Core Workflows

1. Manage Issues

When to use: User wants to create, update, list, or search issues in a GitLab project

Tool sequence:

  1. GITLAB_GET_PROJECTS - Find the target project and get its ID [Prerequisite]
  2. GITLAB_LIST_PROJECT_ISSUES - List and filter issues for a project [Required]
  3. GITLAB_CREATE_PROJECT_ISSUE - Create a new issue [Required for create]
  4. GITLAB_UPDATE_PROJECT_ISSUE - Update an existing issue (title, labels, state, assignees) [Required for update]
  5. GITLAB_LIST_PROJECT_USERS - Find user IDs for assignment [Optional]

Key parameters:

  • id: Project ID (integer) or URL-encoded path (e.g., "my-group/my-project")
  • title: Issue title (required for creation)
  • description: Issue body text (max 1,048,576 characters)
  • labels: Comma-separated label names (e.g., "bug,critical")
  • add_labels / remove_labels: Add or remove labels without replacing all
  • state: Filter by "all", "opened", or "closed"
  • state_event: "close" or "reopen" to change issue state
  • assignee_ids: Array of user IDs; use [0] to unassign all
  • issue_iid: Internal issue ID within the project (required for updates)
  • milestone: Filter by milestone title
  • search: Search in title and description
  • scope: "created_by_me", "assigned_to_me", or "all"
  • page / per_page: Pagination (default per_page: 20)

Read the full file on GitHub · 259 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. 11d ago First seen · 259 lines · 41 tokens per session scan A ccb69342f8bf

Subscribe to this mod's changes

gitlab-automation is a skill published in the GitHub repository ratnesh-maurya/cursor-claude-personas (8 stars, last pushed 5mo ago), licensed MIT. It adds 41 tokens to every session and 3,548 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

ijfw-ship

Use when the user says 'ship it', 'ship this', 'release', 'publish', 'launch', 'deploy', 'go live', 'wrap this up', 'time to ship', or invokes '/ijfw-ship'. Domain-aware release — software (test → tag → push → publish), book (final edit → format → KDP / agent / Substack), campaign (review → schedule → launch →…

FerroxLabs/ijfw · 139 tokens

lov-gh-tidy

Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…

lovstudio/skills · 95 tokens

status

Show a comprehensive project status report with git state, active specs, and suggested next actions.

devobsessed/code-captain · 19 tokens

issue-creation

Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.

Gentleman-Programming/gentle-ai · 30 tokens

work-unit-commits

Plan commits as reviewable work units. Trigger: implementation, commit splitting, chained PRs, or keeping tests and docs with code.

Gentleman-Programming/gentle-ai · 33 tokens

systemic-issue-triage

Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.

Gentleman-Programming/gentle-ai · 57 tokens