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 skills/grandcamel/gitlab-assistant-skills/gitlab-releasenpx skills add grandcamel/GitLab-Assistant-Skills --skill gitlab-releasegit 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-release)<a href="https://agentmods.dev/skills/grandcamel/gitlab-assistant-skills/gitlab-release"><img src="https://agentmods.dev/badge/skills/grandcamel/gitlab-assistant-skills/gitlab-release.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.00050 | $0.01588 |
| Opus 5 | $0.00025 | $0.00794 |
| Sonnet 5 | $0.00010 | $0.00318 |
| Haiku 4.5 | $0.00005 | $0.00159 |
Grade A, and why
gitlab-release 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 4d 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 — 256 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Skill
Release operations for GitLab using the glab CLI.
Quick Reference
| Operation | Command | Risk |
|---|---|---|
| List releases | glab release list |
- |
| View release | glab release view <tag> |
- |
| Create release | glab release create <tag> |
⚠️ |
| Upload assets | glab release upload <tag> <files> |
⚠️ |
| Download assets | glab release download <tag> |
- |
| Delete release | glab release delete <tag> |
⚠️⚠️ |
Risk Legend: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger
When to Use This Skill
ALWAYS use when:
- User wants to work with releases
- User mentions "release", "version", "changelog", "tag" (for releases)
- User wants to publish or distribute software versions
NEVER use when:
- User wants to manage git tags directly (use git commands)
- User wants CI/CD operations (use gitlab-ci instead)
Available Commands
List Releases
glab release list [options]
Options:
| Flag | Description |
|---|---|
-P, --per-page=<n> |
Results per page |
--all |
Get all releases |
Examples:
# List all releases
glab release list
# List with more results
glab release list --per-page=50
View Release Details
glab release view <tag> [options]
Options:
| Flag | Description |
|---|---|
-w, --web |
Open release in browser |
Examples:
# View release details
glab release view v1.0.0
# Open release in browser
glab release view v1.0.0 --web
Create Release
glab release create <tag> [options]
Options:
| Flag | Description |
|---|---|
-n, --notes=<notes> |
Release notes |
-F, --notes-file=<file> |
Read release notes from file |
-N, --name=<name> |
Release name (defaults to tag) |
-r, --ref=<ref> |
Git ref to create tag from (if tag doesn't exist) |
-a, --assets-links=<json> |
JSON array of asset links |
--milestone=<titles> |
Milestone titles to associate |
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.
- 4d ago First seen · 256 lines · 50 tokens per session scan A 9a5169ac9357
gitlab-release is a skill published in the GitHub repository grandcamel/GitLab-Assistant-Skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 50 tokens to every session and 1,588 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
skill-finish-branch
Wrap up a branch — run tests, create PR, merge or discard — use when implementation is done.
deploy-steward
Mainline deploy steward. Consumes ready PRs, owns a lease on mainline landing, refreshes PR state, updates stale branches, waits for CI and deploy gates, merges or queues one candidate at a time, and opens repair tasks for failures.
gitlab-devops
GitLab DevOps operations — issues, merge requests, CI/CD pipelines, repository browsing, labels, milestones, releases, and wiki management. Use when querying GitLab project status, monitoring pipeline executions, browsing repository files, creating issues for network findings, opening merge requests for config…
release
CONTRIBUTOR TOOL - Cut a plugin release: bump plugin.json version, finalize CHANGELOG, update README if needed, gate on make ci, commit, tag vX.Y.Z, and create the GitHub release. Use when shipping a new plugin version. NOT distributed.
release
Cut a brooks-lint release: set the version in package.json, propagate it across all four plugin manifests and every version-bearing text file (README badges, docs site metadata), write the CHANGELOG entry, validate, then commit, push, tag, and publish the GitHub release. Triggers when the maintainer asks to "release"…
new
Use when user asks to create a release, cut a release, or publish a version. Auto-detects GitHub vs GitLab vs Gitea, calculates semantic version, generates release notes from PRs/MRs or commits, shows preview for confirmation before publishing.