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 skills add GantisStorm/essentials-claude-code --skill gitlab-cligit clone --depth 1 https://github.com/GantisStorm/essentials-claude-codeWrote 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/gantisstorm/essentials-claude-code/gitlab-cli)<a href="https://agentmods.dev/skills/gantisstorm/essentials-claude-code/gitlab-cli"><img src="https://agentmods.dev/badge/skills/gantisstorm/essentials-claude-code/gitlab-cli/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.
<a href="https://agentmods.dev/skills/gantisstorm/essentials-claude-code/gitlab-cli"><img src="https://agentmods.dev/badge/skills/gantisstorm/essentials-claude-code/gitlab-cli.svg" alt="Reviewed on agentmods" width="80" 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.00021 | $0.00642 |
| Opus 5.5 | $0.00008 | $0.00257 |
| Sonnet 5.5 | $0.00004 | $0.00128 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
gitlab-cli 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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab CLI helper skill for common glab operations. Requires glab CLI installed and authenticated.
Note: For creating/updating MR descriptions, use /mr-description-creator instead.
Actions
MR Operations
View MR status:
/gitlab-cli mr status
View MR in browser:
/gitlab-cli mr view --web
List MRs:
/gitlab-cli mr list
Merge MR:
/gitlab-cli mr merge
Issue Operations
List issues:
/gitlab-cli issue list
Create issue:
/gitlab-cli issue create
View issue:
/gitlab-cli issue view <number>
CI/CD Operations
View CI status:
/gitlab-cli ci status
View pipeline:
/gitlab-cli ci view
List jobs:
/gitlab-cli job list
Repository Operations
View repo:
/gitlab-cli repo view
Instructions
Step 1: Validate Environment
# Check glab is installed
glab --version
# Check glab is authenticated
glab auth status
If not installed, report: "Install glab CLI: https://gitlab.com/gitlab-org/cli" If not authenticated, report: "Run: glab auth login"
Step 2: Parse and Execute
Parse $ARGUMENTS and pass directly to glab:
glab $ARGUMENTS
Step 3: Report Result
Show glab output directly to user.
Examples
# View MR status
/gitlab-cli mr status
# View MR in browser
/gitlab-cli mr view --web
# List open MRs
/gitlab-cli mr list
# Merge current MR
/gitlab-cli mr merge
# List issues
/gitlab-cli issue list
# Create issue interactively
/gitlab-cli issue create
# View repo info
/gitlab-cli repo view
# View CI status
/gitlab-cli ci status
# View pipeline
/gitlab-cli ci view
# List jobs
/gitlab-cli job list
# API calls
/gitlab-cli api projects/:id/merge_requests
# Any glab command works
/gitlab-cli release list
/gitlab-cli label list
Error Handling
| Scenario | Action |
|---|---|
| glab not installed | "Install glab: https://gitlab.com/gitlab-org/cli" |
| Not authenticated | "Run: glab auth login" |
| glab command fails | Show glab error output |
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.
- 1mo ago First seen · 152 lines · 21 tokens per session scan A b881b78837bf
gitlab-cli is a skill published in the GitHub repository GantisStorm/essentials-claude-code (90 stars, last pushed 8mo ago), licensed Unlicense. It adds 21 tokens to every session and 642 once invoked, about $0.0001 per session on Opus 5.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
deploy-setup
Wire up a freshly scaffolded Starter Series project for its first release — detect the template, register required GitHub secrets, set up OIDC trusted publishing where applicable, and trigger the first CD run. Pairs with the create skill (you scaffold first, then run this).
rhiza-remote
Check what CI on the origin says about this repo's open pull/merge requests, then diagnose and fix the red ones on their own branches. Reads the forge, reproduces locally, pushes fixes to the request's branch — never to the default branch.
repo-hygiene
Use when the scheduled repo-hygiene workflow runs from GitHub Actions (or an operator dry-run) to scan the repository for small, certain docs/test/code hygiene issues and fix them as one batched branch.
create-issue
Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.
docs-update-from-diff
Review local code changes with git diff and update the official docs under docs/ to match. Use when the user asks to document current uncommitted work, sync docs with local changes, update docs after a feature or refactor, or when phrases like "git diff", "local changes", "update docs", or "official docs" appear.
prepare-pr
Prepare GitHub pull request title and body files from the current branch diff, especially for non-interactive CI/autofix flows that must follow the repository PR template without pushing or creating the PR.