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.
git 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/browse-skills)<a href="https://agentmods.dev/commands/grandcamel/gitlab-assistant-skills/browse-skills"><img src="https://agentmods.dev/badge/commands/grandcamel/gitlab-assistant-skills/browse-skills/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/commands/grandcamel/gitlab-assistant-skills/browse-skills"><img src="https://agentmods.dev/badge/commands/grandcamel/gitlab-assistant-skills/browse-skills.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.00010 | $0.00225 |
| Opus 5 | $0.00005 | $0.00112 |
| Sonnet 5 | $0.00002 | $0.00045 |
| Haiku 4.5 | $0.00001 | $0.00022 |
Grade A, and why
browse-skills 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 12d 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
Browse GitLab Skills
List all available GitLab automation skills.
Available Skills
| Skill | Description |
|---|---|
| gitlab-assistant | Hub skill - routes to specialized skills |
| gitlab-mr | Mr operations |
| gitlab-issue | Issue operations |
| gitlab-ci | Ci operations |
| gitlab-repo | Repo operations |
| gitlab-release | Release operations |
| gitlab-label | Label operations |
| gitlab-milestone | Milestone operations |
| gitlab-variable | Variable operations |
Usage
To use a skill, simply describe what you want to do:
- "List all resources" - Routes to appropriate skill
- "Create a new item" - Routes to resource skill
- "Search for X" - Routes to search skill
Getting Started
- Run
/gitlab-assistant-setupto configure authentication - Describe your task naturally
- The assistant will route to the appropriate skill
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.
- 12d ago First seen · 38 lines · 10 tokens per session scan A bc8971ac9366
browse-skills 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 225 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
linear-cleanup
Audit Linear issues for problems (missing labels, stale, duplicates, wrong state, orphaned, unactionable) and propose fixes.
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.
linear-curator-run
Run the curator — collect signals from configured signal sources and report.
linear-sync
Populate or refresh the Linear reference files (teams, projects, users, workflows).
linear-search
Search Linear issues by keyword, team, assignee, state, or priority.
linear-my-issues
List Linear issues assigned to you, grouped by state.