gitlab-variable

A set of commands for managing GitLab CI/CD variables, including environment values and secrets used by automated builds.

In plain words
What is it for?
Use it to list, view, create, update, delete, and export GitLab project or group variables.
Why use it?
It reduces manual work when configuring values that pipelines need, while keeping variable management separate from running pipelines.

Skill for Claude CodeCodex

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.

agentmods
npx agentmods add skills/grandcamel/gitlab-assistant-skills/gitlab-variable
Any agent
npx skills add grandcamel/GitLab-Assistant-Skills --skill gitlab-variable
Clone the repo
git clone --depth 1 https://github.com/grandcamel/GitLab-Assistant-Skills

Made for: Claude Code, Codex.

Per session 53 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,795 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00053 $0.01795
Opus 5 $0.00026 $0.00898
Sonnet 5 $0.00011 $0.00359
Haiku 4.5 $0.00005 $0.00179

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

Security

Grade A, and why

gitlab-variable 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 2d 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.

skills/gitlab-variable/SKILL.md · 270 lines

How it starts

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

CI/CD Variable Skill

CI/CD variable management operations for GitLab using the glab CLI.

Quick Reference

Operation Command Risk
List variables glab variable list -
Get variable glab variable get <key> -
Set variable glab variable set <key> <value> ⚠️
Update variable glab variable update <key> <value> ⚠️
Delete variable glab variable delete <key> ⚠️⚠️
Export variables glab variable export -

Risk Legend: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger

When to Use This Skill

ALWAYS use when:

  • User wants to manage CI/CD variables
  • User mentions "variable", "secret", "env var", "CI variable", "environment variable"
  • User wants to configure build/deployment settings

NEVER use when:

  • User wants to run pipelines (use gitlab-ci)
  • User wants to manage .env files locally (use file operations)

Available Commands

List Variables

glab variable list [options]

Options:

Flag Description
-g, --group=<group> List group-level variables
-P, --per-page=<n> Results per page

Examples:

# List project variables
glab variable list

# List group variables
glab variable list -g mygroup

Get Variable

glab variable get <key> [options]

Options:

Flag Description
-g, --group=<group> Get from group level
-s, --scope=<scope> Variable scope/environment

Examples:

# Get variable value
glab variable get API_KEY

# Get scoped variable
glab variable get DATABASE_URL --scope=production

Set Variable

glab variable set <key> <value> [options]

Options:

Flag Description
-g, --group=<group> Set at group level
-m, --masked Mask value in logs
-p, --protected Only available in protected branches
-r, --raw Value is raw (no expansion)
-s, --scope=<scope> Variable scope/environment
-t, --type=<type> Variable type: env_var, file

Read the full file on GitHub · 270 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. 2d ago First seen · 270 lines · 53 tokens per session scan A 37b33a0df8cb

Subscribe to this mod's changes

gitlab-variable is a skill published in the GitHub repository grandcamel/GitLab-Assistant-Skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 53 tokens to every session and 1,795 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-31.

Related

Other skills, from other repositories

create-mcp-tool

Create a new MCP tool end-to-end: sub-package, input/output structs, handler, ActionSpec metadata, markdown formatter, tests, catalog projection, and documentation. Use when adding a new GitLab API endpoint as an MCP tool.

jmrplens/gitlab-mcp-server · 52 tokens

go-safe-move-refactor

Safely move Go source files between packages with zero compilation downtime. Handles package declarations, import updates, symbol exports, type renames, test migration, and forwarding stubs. Validates compilation after every atomic step.

jmrplens/gitlab-mcp-server · 50 tokens

go-source-documentation

Add idiomatic, godoc-compliant documentation to Go source and test files. Use when user asks to document Go files, add doc comments, improve Go documentation, or mentions /document-go. Covers file headers, package comments, types, functions, interfaces, constants, variables, tests (with detailed explanations)…

jmrplens/gitlab-mcp-server · 75 tokens

increase-test-coverage

Increase Go test coverage to 90%+ using a Research → Plan → Implement pipeline. Analyzes coverage gaps, generates table-driven tests with httptest mocks, and validates results with go test -coverprofile. Designed for Go MCP server projects using the official go-sdk and gitlab.com/gitlab-org/api/client-go/v2.

jmrplens/gitlab-mcp-server · 72 tokens

modularize-go-package

Modularize a monolithic Go package into domain-specific sub-packages. Extracts shared utilities, moves domain files, updates imports, renames types, creates registration functions, and validates compilation+tests at every step. Designed for large-scale refactoring of 50-100+ file packages.

jmrplens/gitlab-mcp-server · 65 tokens

generate-project-documentation

Generate comprehensive project documentation including architecture overview, package/component docs, MCP tools/resources/prompts reference, developer onboarding guide, and configuration/deployment guide. Uses Diátaxis framework and Mermaid diagrams.

jmrplens/gitlab-mcp-server · 43 tokens