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 vince-winkintel/gitlab-cli-skills --skill glab-incidentgit clone --depth 1 https://github.com/vince-winkintel/gitlab-cli-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/vince-winkintel/gitlab-cli-skills/glab-incident)<a href="https://agentmods.dev/skills/vince-winkintel/gitlab-cli-skills/glab-incident"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-incident/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/skills/vince-winkintel/gitlab-cli-skills/glab-incident"><img src="https://agentmods.dev/badge/skills/vince-winkintel/gitlab-cli-skills/glab-incident.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00045 | $0.00878 |
| Opus 5.5 | $0.00018 | $0.00351 |
| Sonnet 5.5 | $0.00009 | $0.00176 |
| Haiku 4.5 | $0.00005 | $0.00088 |
Grade A, and why
glab-incident 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 2d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
glab incident
Capture key
685c1cbd7: checksum-verified macOS arm64 binary, source commit685c1cbd74c882e0c93d7011657adde811582ed7; archive SHA-256e77f5756c3c8d9ffeaef0bf234533f395680ab9f128a75cec4c1bd7a1049788c. Only fences marked685c1cbd7use this capture. Normalization removes trailing spaces/tabs only; indentation, blank lines, wrapping, truncation, and product spelling (includingGitlab) are preserved. Other fences retain their individual prior provenance.
Open-item selection
glab incident list defaults to open items. Omit the obsolete --opened flag; use --closed or --all for those scopes. This applies to the shared issue/incident list command, including its ls alias, and is separate from MR state selectors.
Internal notes
glab incident note 123 --internal --message "Incident details for project members" requests an internal note visible only to project members. Verify the target incident and intended audience before posting; internal notes are not a place to store credentials. Incident list uses the shared issue date and assignment filters, including --assignee @none and --assignee @any.
Overview
Incidents track service disruptions and their resolution. List and
view incidents, comment on them, and subscribe, close, or reopen
them.
Use `--repo` to target a project other than the current one.
USAGE
glab incident [command] [--flags]
EXAMPLES
glab incident list
COMMANDS
close [<id> | <url>] [--flags] Close an incident.
list [--flags] List project incidents.
note <incident-id> [--flags] Comment on an incident in GitLab.
reopen [<id> | <url>] [--flags] Reopen a resolved incident.
subscribe <id> Subscribe to an incident.
unsubscribe <id> Unsubscribe from an incident.
view <id> [--flags] Display the title, body, and other information about an incident.
FLAGS
-h --help Show help for this command.
-R --repo Select another repository. You can use either OWNER/REPO or GROUP/NAMESPACE/REPO. The full URL or Git URL is also accepted.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · +7 lines f13a3d71a72f
- 9d ago Changed · +4 lines fe4169e651ab
- 16d ago Changed · +10 lines 22246944cf6a
- 23d ago Changed · +2 lines e052b00019a1
- 1mo ago Changed · +7 lines ac33ac45f455
- 2mo ago First seen · 47 lines · 45 tokens per session scan A ffe850794452
glab-incident is a skill published in the GitHub repository vince-winkintel/gitlab-cli-skills (49 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 878 once invoked, about $0.0002 per session on Opus 5.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-30.
Other skills, from other repositories
bug-triage
Re-evaluate open bugs — priority vs severity, assign to sprints, surface systemic trends. Run when the count grows.
triage-issue-reports
Triage Slack issue reports with one thread-only verdict, evidence review, cause-aware routing, tracker dedupe, and fail-closed ticket creation. Use only from the configured Benny triage automation.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
moai-lane-watchdog
One lane stall watchdog iteration: measure lane progress on three channels, classify the stall cause, apply the remedy or resolve the judgment through the decision ladder — instead of waiting on a reply — then record the outcome and report. Reads the unified --auto doctrine at…
investigation
Create an investigation ticket + live-doc for sustained root-cause work (retros, bug archaeology, regression hunts).