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 agentmods add commands/grandcamel/gitlab-assistant-skills/gitlab-assistant-setupgit clone --depth 1 https://github.com/grandcamel/GitLab-Assistant-SkillsWrote 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/commands/grandcamel/gitlab-assistant-skills/gitlab-assistant-setup)<a href="https://agentmods.dev/commands/grandcamel/gitlab-assistant-skills/gitlab-assistant-setup"><img src="https://agentmods.dev/badge/commands/grandcamel/gitlab-assistant-skills/gitlab-assistant-setup.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.00185 |
| Opus 5 | $0.00005 | $0.00093 |
| Sonnet 5 | $0.00002 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
gitlab-assistant-setup 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 3d 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.
What it actually says
GitLab Assistant Setup
Set up GitLab Assistant Skills for Claude Code.
Prerequisites
Install the glab CLI:
brew install glab
Authentication
Authenticate with GitLab:
glab auth login
Verification
Verify your setup:
glab auth status
Configuration
Configuration is stored in your glab CLI config.
Troubleshooting
| Issue | Solution |
|---|---|
| Auth failed | Run glab auth login again |
| CLI not found | Verify installation: which glab |
| Permission denied | Check your GitLab permissions |
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.
- 3d ago First seen · 50 lines · 10 tokens per session scan A 005b1c576bcc
gitlab-assistant-setup is a command published in the GitHub repository grandcamel/GitLab-Assistant-Skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 10 tokens to every session and 185 once invoked, about $0.0001 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.
Other commands, from other repositories
smoke
Smoke-test the agent-smith CLI binary + docker-compose for api-scan / security-scan / fix-bug. Catches regressions that escape the unit test suite.
review-solo
One agent applies all six review lenses + self-verifies in a single pass — the CLI counterpart of managed's AIRREVIEWMODE=solo, sharing the same assembled prompt (lib/soloprompt.py) and the same verdict-gating contract (lib/verdict.py). Runs on Fable via your Claude Code subscription: 3–7 min of agent time and $0 of…
learn
Clean up, deduplicate, and reorganize the wiki REVIEW.md using AI. Also regenerates REVIEW-HISTORY.md from PR comment history.
review-respond
When --respond is passed, this flow automates the developer's side of the review cycle. It reads the existing review, classifies each finding based on local code changes, verifies fixes are correct, runs a self-check on the fix diff, detects additional changes, and posts a structured response that the reviewer's next…
review
Automated code review with verification, pattern learning, and team knowledge — review PRs, self-check before pushing, or track fixes across iterations.
review-self
When --self is passed, this is a completely different flow. No PR needed. Reviews local changes before push.