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-issuenpx skills add grandcamel/GitLab-Assistant-Skills --skill gitlab-issuegit 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-issue)<a href="https://agentmods.dev/skills/grandcamel/gitlab-assistant-skills/gitlab-issue"><img src="https://agentmods.dev/badge/skills/grandcamel/gitlab-assistant-skills/gitlab-issue.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.00059 | $0.01953 |
| Opus 5 | $0.00030 | $0.00977 |
| Sonnet 5 | $0.00012 | $0.00391 |
| Haiku 4.5 | $0.00006 | $0.00195 |
Grade A, and why
gitlab-issue 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 — 292 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Skill
Issue operations for GitLab using the glab CLI.
Quick Reference
| Operation | Command | Risk |
|---|---|---|
| List issues | glab issue list |
- |
| View issue | glab issue view <id> |
- |
| Create issue | glab issue create |
⚠️ |
| Update issue | glab issue update <id> |
⚠️ |
| Close issue | glab issue close <id> |
⚠️ |
| Reopen issue | glab issue reopen <id> |
⚠️ |
| Delete issue | glab issue delete <id> |
⚠️⚠️ |
| Add note | glab issue note <id> |
⚠️ |
Risk Legend: - Safe | ⚠️ Caution | ⚠️⚠️ Warning | ⚠️⚠️⚠️ Danger
When to Use This Skill
ALWAYS use when:
- User wants to work with issues
- User mentions "issue", "bug", "task", "ticket" or related terms
- User wants to track or manage work items
NEVER use when:
- User wants bulk operations on 10+ issues (use gitlab-bulk instead)
- User is only searching/filtering issues (use gitlab-search instead)
Available Commands
List Issues
glab issue list [options]
Options:
| Flag | Description |
|---|---|
-a, --assignee=<user> |
Filter by assignee (use @me for yourself) |
--author=<user> |
Filter by author |
-l, --label=<labels> |
Filter by comma-separated labels |
-m, --milestone=<milestone> |
Filter by milestone |
-s, --state=<state> |
Filter by state: opened, closed, all (default: opened) |
-c, --closed |
Get only closed issues |
--all |
Get all issues |
-P, --per-page=<n> |
Number of items per page |
--confidential |
Filter to only confidential issues |
--search=<query> |
Search issues by title/description |
Examples:
# List all open issues
glab issue list
# List issues assigned to you
glab issue list --assignee=@me
# List closed issues
glab issue list --closed
# List issues with specific label
glab issue list --label=bug
# List issues in a milestone
glab issue list --milestone="Release 1.0"
# Search issues
glab issue list --search="login bug"
# Get all issues (paginated)
glab issue list --all
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 · 292 lines · 59 tokens per session scan A 357c80dbdc5d
gitlab-issue is a skill published in the GitHub repository grandcamel/GitLab-Assistant-Skills (4 stars, last pushed 7mo ago), licensed MIT. It adds 59 tokens to every session and 1,953 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
asana-sweep
Scheduled sweep of incomplete Asana tasks assigned to you — triage into auto/ask/skip, dedupe against existing work, then call asana-to-harness to open GitLab issues that trigger an AI coding harness. Built for headless scheduled runs (claude -p); also runs interactively, with --dry-run support.
asana-to-harness
Turn one Asana task into an implementation plan for an AI coding harness, open a GitLab issue with the plan as its description, and leave a trigger comment (e.g. @claude). Used standalone ("turn this Asana task into a harness issue") or invoked by the asana-sweep skill.
create-app
Guided journey from a raw app idea to a validated, cleanly architected first version that ships on a sustainable cadence. Orchestrates ten skills phase by phase - lean-startup, design-sprint, clean-architecture, domain-driven-design, clean-code, pragmatic-programmer, system-design, ios-hig-design, 37signals-way…
create-business
Guided journey from raw idea to a validated, positioned, priced business with a chosen beachhead. Orchestrates ten skills phase by phase - jobs-to-be-done, mom-test, design-sprint, lean-startup, good-strategy-bad-strategy, blue-ocean-strategy, obviously-awesome, hundred-million-offers, monetizing-innovation…
requirement-forge-refiner
Facilitate a structured conversation to define requirement standards for a project — epic and feature definitions, scenario structure, AC format, priority notation, status workflow, and naming conventions. Produces a formal requirement-standards.md that the requirement-quality atom reads via config resolution…
glab
Expert guidance for using the GitLab CLI (glab) to manage GitLab issues, merge requests, CI/CD pipelines, repositories, and other GitLab operations from the command line. Use this skill when the user needs to interact with GitLab resources or perform GitLab workflows.