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 arnabdeypolimi/claude_code_setup --skill gitlab-integrationgit clone --depth 1 https://github.com/arnabdeypolimi/claude_code_setupWrote 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/arnabdeypolimi/claude_code_setup/gitlab-integration)<a href="https://agentmods.dev/skills/arnabdeypolimi/claude_code_setup/gitlab-integration"><img src="https://agentmods.dev/badge/skills/arnabdeypolimi/claude_code_setup/gitlab-integration/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/arnabdeypolimi/claude_code_setup/gitlab-integration"><img src="https://agentmods.dev/badge/skills/arnabdeypolimi/claude_code_setup/gitlab-integration.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.00058 | $0.01208 |
| Opus 5.5 | $0.00023 | $0.00483 |
| Sonnet 5.5 | $0.00012 | $0.00242 |
| Haiku 4.5 | $0.00006 | $0.00121 |
Grade A, and why
gitlab-integration 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab Integration
Patterns for interacting with GitLab via the glab CLI.
Authentication
Check Auth Status
glab auth status
Login
glab auth login
glab auth login --token <token>
Merge Requests
Create MR
# Basic
glab mr create --title "Title" --description "Description"
# With target branch
glab mr create --title "Title" --target-branch main
# With labels and assignee
glab mr create --title "Title" --label "feature,priority:high" --assignee username
# Draft MR
glab mr create --title "Draft: Title" --draft
Create MR via Push Options
git push -o merge_request.create \
-o merge_request.target=<branch> \
-o merge_request.title="Title" \
-o merge_request.description="Description" \
-o merge_request.label="label1,label2" \
-o merge_request.assignee="username" \
-o merge_request.remove_source_branch
List MRs
glab mr list # All open MRs
glab mr list --state opened|merged|closed
glab mr list --target-branch=main
glab mr list --author=username
glab mr list --assignee=@me
glab mr list --label="feature"
View MR
glab mr view <id> # View details
glab mr view <id> --comments # View with comments
glab mr view <id> --web # View in browser
glab mr diff <id> # View diff
Update MR
glab mr update <id> --title "New Title"
glab mr update <id> --description "New description"
glab mr update <id> --label "new-label"
glab mr update <id> --ready # Mark ready (remove draft)
MR Actions
glab mr approve <id>
glab mr merge <id>
glab mr merge <id> --squash
glab mr close <id>
glab mr reopen <id>
MR Comments
glab mr comment <id> --message "Comment text"
glab mr note <id> "Note text"
Issues
List Issues
glab issue list # All open issues
glab issue list --state opened|closed
glab issue list --label "bug"
glab issue list --assignee @me
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 · 222 lines · 58 tokens per session scan A 77d5019b92f8
gitlab-integration is a skill published in the GitHub repository arnabdeypolimi/claude_code_setup (4 stars, last pushed 1mo ago), licensed MIT. It adds 58 tokens to every session and 1,208 once invoked, about $0.0002 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-31.
Other skills, from other repositories
deployment-patterns
Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
turborepo-caching
Configure Turborepo for efficient monorepo builds with local and remote caching. Use when setting up Turborepo, optimizing build pipelines, or implementing distributed caching.
bitbucket-workflow
Bitbucket best practices for pull requests, Pipelines CI/CD, Jira integration, and Atlassian ecosystem workflows.
gitlab-workflow
GitLab best practices for merge requests, CI/CD pipelines, issue tracking, and DevOps workflows.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.