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-badgegit 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-badge)<a href="https://agentmods.dev/skills/grandcamel/gitlab-assistant-skills/gitlab-badge"><img src="https://agentmods.dev/badge/skills/grandcamel/gitlab-assistant-skills/gitlab-badge.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.00052 | $0.02664 |
| Opus 5 | $0.00026 | $0.01332 |
| Sonnet 5 | $0.00010 | $0.00533 |
| Haiku 4.5 | $0.00005 | $0.00266 |
Grade A, and why
gitlab-badge 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 7d 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 — 310 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Badge Skill
Project badge management for GitLab using glab api raw endpoint calls.
Quick Reference
| Operation | Command Pattern | Risk |
|---|---|---|
| List badges | glab api projects/:id/badges |
- |
| Get badge | glab api projects/:id/badges/:badge_id |
- |
| Create badge | glab api projects/:id/badges -X POST -f ... |
⚠️ |
| Update badge | glab api projects/:id/badges/:badge_id -X PUT -f ... |
⚠️ |
| Delete badge | glab api projects/:id/badges/:badge_id -X DELETE |
⚠️ |
| Preview badge | glab api projects/:id/badges/render?... |
- |
| List group badges | glab api groups/:id/badges |
- |
Risk Legend: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger
When to Use This Skill
ALWAYS use when:
- User mentions "badge", "status badge", "coverage badge"
- User wants to add badges to README
- User wants pipeline or build status indicators
- User mentions badge links or badge images
NEVER use when:
- User wants labels on issues/MRs (use gitlab-label)
- User wants status of pipelines (use gitlab-ci)
- User wants project settings (use gitlab-repo)
API Prerequisites
Required Token Scopes: api
Permissions:
- Read badges: Reporter+
- Manage badges: Maintainer+
Badge Placeholders
GitLab supports placeholders in badge URLs:
| Placeholder | Description |
|---|---|
%{project_path} |
Full project path (e.g., group/project) |
%{project_id} |
Numeric project ID |
%{project_name} |
Project name |
%{project_namespace} |
Project namespace |
%{default_branch} |
Default branch name |
%{commit_sha} |
Current commit SHA |
Available Commands
List Project Badges
# List all project badges
glab api projects/123/badges --method GET
# Using project path
glab api "projects/$(echo 'mygroup/myproject' | jq -Rr @uri)/badges"
List Group Badges
# List group badges (inherited by projects)
glab api groups/456/badges --method GET
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.
- 7d ago First seen · 310 lines · 52 tokens per session scan A 3a55e1130292
gitlab-badge is a skill published in the GitHub repository grandcamel/GitLab-Assistant-Skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 52 tokens to every session and 2,664 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-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.
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.