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 peteroden/jira-and-gitlab-skills --skill gitlabgit clone --depth 1 https://github.com/peteroden/jira-and-gitlab-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/peteroden/jira-and-gitlab-skills/gitlab)<a href="https://agentmods.dev/skills/peteroden/jira-and-gitlab-skills/gitlab"><img src="https://agentmods.dev/badge/skills/peteroden/jira-and-gitlab-skills/gitlab.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.00098 | $0.02086 |
| Opus 5 | $0.00049 | $0.01043 |
| Sonnet 5 | $0.00020 | $0.00417 |
| Haiku 4.5 | $0.00010 | $0.00209 |
Grade A, and why
gitlab 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prerequisites
The script at .github/skills/gitlab/gitlab requires python3 (3.6+).
Environment variables (must be set before running any command):
| Variable | Required | Purpose |
|---|---|---|
GITLAB_URL |
Always | Instance URL (e.g., https://gitlab.com or https://gitlab.company.com) |
GITLAB_TOKEN |
Always | Personal access token (sent as PRIVATE-TOKEN header) |
GITLAB_PROJECT |
Optional | Project ID or URL-encoded path (e.g., 12345 or group%2Fproject) |
Project auto-detection: If GITLAB_PROJECT is not set, the script parses git remote get-url origin to extract the project path. This works for both SSH and HTTPS remotes. Set GITLAB_PROJECT explicitly when not in a git repo or targeting a different project.
Output Modes
All read commands (mr-list, mr-get, mr-notes, pipeline-get, pipeline-jobs) support a --fields flag that extracts specific fields using dot-notation, outputting tab-separated values instead of raw JSON. Always use --fields by default to keep output concise:
.github/skills/gitlab/gitlab mr-list opened --fields iid,title,author.name,user_notes_count
.github/skills/gitlab/gitlab mr-get 42 --fields iid,title,state,source_branch,target_branch
.github/skills/gitlab/gitlab mr-notes 42 --fields author.name,created_at,body
For lists, output includes a header row. For single items, output is field: value per line. Nested fields use dot-notation (e.g. author.name). Omit --fields only when the full JSON is needed.
Command Reference
All commands use the full path: .github/skills/gitlab/gitlab <command> [args...]
Merge Requests
| Command | Purpose | Syntax |
|---|---|---|
mr-list |
List merge requests | .github/skills/gitlab/gitlab mr-list [state] [max] |
mr-get |
Fetch MR details | .github/skills/gitlab/gitlab mr-get <MR-IID> |
mr-create |
Create a new MR | .github/skills/gitlab/gitlab mr-create '<json>' |
mr-update |
Update MR fields | .github/skills/gitlab/gitlab mr-update <MR-IID> '<json>' |
mr-comment |
Add a comment/note | .github/skills/gitlab/gitlab mr-comment <MR-IID> '<body>' |
mr-notes |
List MR comments | .github/skills/gitlab/gitlab mr-notes <MR-IID> [max] |
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.
- 7d ago First seen · 205 lines · 98 tokens per session scan A 32399d079d07
gitlab is a skill published in the GitHub repository peteroden/jira-and-gitlab-skills (5 stars, last pushed 6mo ago), licensed MIT. It adds 98 tokens to every session and 2,086 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-08-31.
Other skills, from other repositories
agent-github-modes
Agent skill for github-modes - invoke with $agent-github-modes.
chinese-git-workflow
A reference for configuring Git with Chinese code-hosting services such as Gitee, Coding.net, GitLab China, and CNB, including SSH, HTTPS, credentials, CI, and repository mirroring.
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
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.
triage
Activate for the daily repository triage run, or when the user asks to triage CI failures, open issues, or recent commits. Reads yesterday's signals, dedupes against the state file, drafts fixes in isolated worktrees with a reviewer pass, opens PRs on green, and keeps people out of limbo with comments in the…
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.