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 serejaris/kimi-skills --skill glab-issuegit clone --depth 1 https://github.com/serejaris/kimi-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/serejaris/kimi-skills/glab-issue)<a href="https://agentmods.dev/skills/serejaris/kimi-skills/glab-issue"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/glab-issue/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/serejaris/kimi-skills/glab-issue"><img src="https://agentmods.dev/badge/skills/serejaris/kimi-skills/glab-issue.svg" alt="Reviewed on agentmods" width="80" 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.00104 | $0.01058 |
| Opus 5 | $0.00052 | $0.00529 |
| Sonnet 5 | $0.00021 | $0.00212 |
| Haiku 4.5 | $0.00010 | $0.00106 |
Grade A, and why
glab-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 9d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
glab issue
创建、查看、更新和管理 GitLab 议题（issue）。
快速入门
# Create an issue
glab issue create --title "Fix login bug" --label bug
# List open issues
glab issue list --state opened
# View issue details
glab issue view 123
# Add comment
glab issue note 123 -m "Working on this now"
# Close issue
glab issue close 123
常用工作流
缺陷报告工作流
-
创建缺陷议题：
glab issue create \ --title "Login fails with 500 error" \ --label bug \ --label priority::high \ --assignee @dev-lead -
添加复现步骤：
glab issue note 456 -m "Steps to reproduce: 1. Navigate to /login 2. Enter valid credentials 3. Click submit Expected: Dashboard loads Actual: 500 error"
议题分类
-
列出未分类的议题：
glab issue list --label needs-triage --state opened -
更新标签和指派人：
glab issue update 789 \ --label backend,priority::medium \ --assignee @backend-team \ --milestone "Sprint 23" -
移除分类标签：
glab issue update 789 --unlabel needs-triage
批量打标签：
对多个议题批量添加标签：
scripts/batch-label-issues.sh "priority::high" 100 101 102
scripts/batch-label-issues.sh bug 200 201 202 203
Sprint 规划
查看当前 Sprint 的议题：
glab issue list --milestone "Sprint 23" --assignee @me
添加到 Sprint：
glab issue update 456 --milestone "Sprint 23"
看板视图：
glab issue board view
将议题关联到工作
为议题创建 MR：
glab mr for 456 # Creates MR that closes issue #456
自动化工作流（创建分支 + 草稿 MR）：
scripts/create-mr-from-issue.sh 456 --create-mr
该脚本自动完成：从议题标题创建分支 → 空提交 → 推送 → 创建草稿 MR。
通过提交/MR 关闭议题：
git commit -m "Fix login bug
Closes #456"
相关技能
从议题创建 MR：
- 参见
glab-mr了解合并请求操作 - 使用
glab mr for <issue-id>创建可关闭议题的 MR - 脚本：
scripts/create-mr-from-issue.sh自动化分支创建 + 草稿 MR
标签管理：
- 参见
glab-label了解标签的创建和管理 - 脚本：
scripts/batch-label-issues.sh用于批量打标签操作
项目规划：
- 参见
glab-milestone了解版本规划 - 参见
glab-iteration了解 Sprint/迭代管理
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.
- 9d ago First seen · 148 lines · 104 tokens per session scan A 0d462d123c3e
glab-issue is a skill published in the GitHub repository serejaris/kimi-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 1,058 once invoked, about $0.0005 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-09-03.
Other skills, from other repositories
syndic
Gère un parc de copropriétés en France avec vue portfolio consolidée. Couvre administration, comptabilité (décret 2005, plan comptable copro, 5 annexes), assemblées générales (convocation, PV, notification), appels de fonds, travaux, fournisseurs, recouvrement d'impayés et transition de syndic. Maîtrise les majorités…
implement-improvements
Validate improvements from .turbo/improvements.md, recommend a working set tailored to what's in the backlog, and run one lane: direct fixes, investigation, or planned work. One lane per session. Use when the user asks to "implement improvements", "work on improvements", "address improvements", "process improvement…
note-improvement
Capture an out-of-scope improvement opportunity so it doesn't get lost. Use when the user asks to "note improvement", "save improvement", "track this for later", "remember this improvement", "note this idea", "log improvement", "backlog this", or "park this idea". Also invoke proactively when noticing something…
create-issue
Create a GitHub issue with a drafted title and body. Use when the user asks to "create an issue", "file an issue", "open an issue", "submit an issue", "report a bug", "file a bug report", "file a feature request", or "file a design proposal".
pick-next-issue
Fetch and rank open GitHub issues by community engagement, present the top 3 candidates, and plan implementation for the selected issue. Use when the user asks to "pick next issue", "next issue", "which issue should I work on", "top issues", "most popular issues", "prioritize issues", or "what should I work on next".
split-and-ship
Execute an approved split plan, shipping each change group separately as its own branch and PR or as sequential commits on the current branch. Use when the user asks to "split and ship", "ship the split plan", "create separate PRs", or "split changes into branches".