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 grandcamel/GitLab-Assistant-Skills --skill gitlab-searchgit 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/skills/grandcamel/gitlab-assistant-skills/gitlab-search)<a href="https://agentmods.dev/skills/grandcamel/gitlab-assistant-skills/gitlab-search"><img src="https://agentmods.dev/badge/skills/grandcamel/gitlab-assistant-skills/gitlab-search.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.1 | $0.00061 | $0.02672 |
| Opus 5 | $0.00030 | $0.01336 |
| Sonnet 5 | $0.00012 | $0.00534 |
| Haiku 4.5 | $0.00006 | $0.00267 |
Grade A, and why
gitlab-search 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 6d 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 — 303 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Search Skill
Search operations for GitLab using glab api raw endpoint calls.
Quick Reference
| Operation | Command Pattern | Risk |
|---|---|---|
| Search projects | glab api "search?scope=projects&search=..." |
- |
| Search issues | glab api "search?scope=issues&search=..." |
- |
| Search MRs | glab api "search?scope=merge_requests&search=..." |
- |
| Search code | glab api "search?scope=blobs&search=..." |
- |
| Search commits | glab api "search?scope=commits&search=..." |
- |
| Search users | glab api "search?scope=users&search=..." |
- |
| Search wiki | glab api "search?scope=wiki_blobs&search=..." |
- |
| Project search | glab api "projects/:id/search?scope=...&search=..." |
- |
| Group search | glab api "groups/:id/search?scope=...&search=..." |
- |
Risk Legend: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger
When to Use This Skill
ALWAYS use when:
- User wants to search or find something across GitLab
- User mentions "search", "find", "query", "look for"
- User asks "where is", "which project has", "find all"
- User wants to search code, issues, MRs, commits, or wikis
NEVER use when:
- User wants to list all items (use specific skill: gitlab-issue, gitlab-mr, etc.)
- User knows the exact project/issue/MR ID
- User wants to search local files (use grep/find locally)
API Prerequisites
Required Token Scopes: read_api or api
Note: Search results are limited to resources the authenticated user can access.
Search Scopes
| Scope | Description | Available At |
|---|---|---|
projects |
Search project names/descriptions | Global, Group |
issues |
Search issue titles/descriptions | Global, Group, Project |
merge_requests |
Search MR titles/descriptions | Global, Group, Project |
milestones |
Search milestone titles | Global, Group, Project |
snippet_titles |
Search snippet titles | Global |
wiki_blobs |
Search wiki content | Global, Group, Project |
commits |
Search commit messages | Global, Group, Project |
blobs |
Search code/file content | Global, Group, Project |
notes |
Search comments | Global, Group, Project |
users |
Search usernames/names | Global |
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.
- 6d ago First seen · 303 lines · 61 tokens per session scan A 8ab909734b89
gitlab-search is a skill published in the GitHub repository grandcamel/GitLab-Assistant-Skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 61 tokens to every session and 2,672 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.
Other skills, from other repositories
implement-issue
Take a GitHub issue from planning to PR, resumable across clarification waits.
github-cli
GitHub CLI (gh) wrapper for PR status, issues, and repository operations.
gitlab-cli
GitLab CLI (glab) wrapper for MR status, issues, and repository operations.
atmos-hooks
Atmos hooks: lifecycle events, hook kinds, command/store/git/security hooks, step/steps hooks, when: conditions, scoping and overrides, toolchain integration, --skip-hooks, and Atmos Pro/local output.
atmos-pro
Atmos Pro setup and workflows: settings.pro, GitHub OIDC, affected and inventory uploads, stack locks, pro commit, workflow dispatch, merge queues, and drift detection.
atmos-git
Atmos Git and GitOps: git.repositories, clone/pull/status/diff/commit/push/clean, local Git hook shims, signed commits, managed workdirs, fork-PR trust gate, and auth via identities or github/sts.