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/alirezasoltanijazi/skillnir/gitlabnpx skills add AlirezaSoltaniJazi/Skillnir --skill gitlabgit clone --depth 1 https://github.com/AlirezaSoltaniJazi/SkillnirWhat 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.00135 | $0.02703 |
| Opus 5 | $0.00068 | $0.01352 |
| Sonnet 5 | $0.00027 | $0.00541 |
| Haiku 4.5 | $0.00014 | $0.00270 |
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 3d 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 — 139 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Before You Start
Read LEARNED.md first. It holds corrections, preferences, and per-repo conventions (branch style, target branch, MR-template path, label taxonomy, the linked Jira review status, and any glab flag differences confirmed on this machine). Every rule there overrides defaults in this skill.
Announce skill usage. Say "Using: gitlab skill" at the very start of your response before doing any work.
Preflight: run glab auth status. If glab is not installed, tell the user to install the GitLab CLI (glab) and run glab auth login — never guess credentials. Confirm exact flags with glab mr create --help on first use and record any differences to LEARNED.md (flag names can vary by glab version).
When to Use
- Raising a merge request following the repo's convention
- Creating a convention-named branch for a Jira ticket
- Committing with the repo's ticket-prefixed subject format
- Building an MR description from the diff + the repo's MR template
- Applying labels / milestone and updating the linked Jira ticket
Do NOT Use
- GitHub pull requests — use github.
- Creating or transitioning Jira tickets as the primary task — use jira. This skill only updates the linked ticket at the end of the MR flow.
- CI/CD pipeline files (
.gitlab-ci.yml) — use devopsEngineer. - Never add file paths / code to the Jira ticket — keep the ticket non-technical; technical detail goes in the MR description.
Access & Convention Detection
| Fact | Value |
|---|---|
| Tool | glab CLI (authenticated) + git |
| Project | Auto-resolved from the current repo — never hardcode |
| Target branch | Detect, don't assume (often main or master) |
| Terminology | GitLab uses Merge Request (MR), not Pull Request |
What ships with it
9 files 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.
- INJECT.md 803 B
- LEARNED.md 747 B
- references/ai-interaction-guide.md 7.8 KB
- references/branch-naming.md 3.7 KB
- references/commit-conventions.md 5.2 KB
- references/glab-recipes.md 7.7 KB
- references/labels-and-milestones.md 5.6 KB
- references/mr-templates.md 4.8 KB
- scripts/validate-gitlab.sh 764 B runs code
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.
- 3d ago First seen · 139 lines · 135 tokens per session scan A ae022a434e39
gitlab is a skill published in the GitHub repository AlirezaSoltaniJazi/Skillnir (7 stars, last pushed 1mo ago), licensed MIT. It adds 135 tokens to every session and 2,703 once invoked, about $0.0007 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
git-workflow-and-versioning
Structures git workflow practices. Use when making any code change. Use when committing, branching, resolving conflicts, opening or reviewing a pull request (PR), pushing to a remote, or when you need to organize work across multiple parallel streams. Use when cutting a release, choosing a semantic version bump…
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
git-workflow
This skill should be used when the user asks to "create git commit", "manage branches", "follow git workflow", "use Conventional Commits", "handle merge conflicts", or asks about git branching strategies, version control best practices, pull request workflows. Provides comprehensive Git workflow guidance for team…
commits
Use this skill whenever the user asks to commit changes, write or fix a commit message, amend or rename a commit, or do a workflow that includes committing in the IntelliJ repository. This is a thin repo-specific overlay: use IntelliJ commit format, write full commit messages by default, and keep requested suffixes…
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…