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 ulises-jeremias/agent-toolkit --skill gitlab-cli-workflowgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/gitlab-cli-workflow)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/gitlab-cli-workflow"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/gitlab-cli-workflow/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/ulises-jeremias/agent-toolkit/gitlab-cli-workflow"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/gitlab-cli-workflow.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.00037 | $0.00460 |
| Opus 5.5 | $0.00015 | $0.00184 |
| Sonnet 5.5 | $0.00007 | $0.00092 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
gitlab-cli-workflow 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 1mo 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.
What it actually says
GitLab CLI — draft MR (HOW)
Use this skill when the remote is GitLab and you need to push and open a draft merge request. Workflow skills delegate here.
Prerequisites
glabauthenticated for the host (glab auth status).- Branch pushed to the documented remote.
Discover draft flags
Run glab mr create --help on the machine—subcommands and flags evolve. Prefer draft / WIP equivalents when available.
Recommended flow
- Push the branch and set upstream per team practice.
- Create an MR body file: use the project’s merge request template when present. If the project has no template, you may align the Markdown with
pr-fallback(same default sections as the org PR body) andoutput-handshakefor where the description file lives and human review—then use that file for--descriptionor the equivalent. - Draft MR (illustrative; confirm flags with
glab --help):
glab mr create --draft --title "YOUR_TITLE" --description "$(cat /path/to/body.md)"
If the CLI prefers a file flag, use that instead of shell substitution.
- If draft creation fails, retry with non-draft only if the user accepts, and note the limitation in chat.
Fallback (CLI failure)
- Write untracked
MERGE_REQUEST_DESCRIPTION_<WORK_ITEM_ID>.md(orPR_DESCRIPTION_<ID>.md) with title + body. - Do not
git addit. - Instruct the user to open the GitLab New merge request UI from the branch and paste content, choosing draft if the UI offers it.
Safety
- No secrets in MR descriptions.
- No force-push to shared defaults without explicit user request.
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.
- 1mo ago First seen · 45 lines · 37 tokens per session scan A dc6f673c9f44
gitlab-cli-workflow is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed yesterday), licensed MIT. It adds 37 tokens to every session and 460 once invoked, about $0.0001 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-09-04.
Other skills, from other repositories
github-navigator
GitHub operations via gh CLI. CRITICAL: Use instead of WebFetch for any github.com URL or GitHub repo path like owner/repo. Use when the user asks to inspect repositories, files, issues, pull requests, releases, Actions runs, or repository structure. Use when the user says 'show README', 'list issues', 'check PR'…
active-review
Use when the user wants to prepare for a manual PR code review and asks for help targeting it — a terse PR summary, ranked files to read first, and paste-ready inline comment drafts with GitHub deep-links. Triggers: "active review this PR", "walk me through this PR", "help me review this", "give me inline comments to…
analyze-knowledge
Use when the user asks who knows specific code, who should review a PR or files, what the lottery factor is, whether knowledge is concentrated or spread, who to talk to about a code area, or when suggesting reviewers beyond GitHub's built-in suggestions.
bisect
Use when hunting a regression, phrases like "bisect", "find the commit that broke X", "this used to work", "regression in test Y", "when did start". Also use when escalated from ci-debug-loop because log analysis can't pinpoint the offending change, or when a previously-passing test/build/behavior is now failing and…
fix-pr-conflict
Resolve merge conflicts on a pull request by rebasing onto the base branch. Use when a PR is not mergeable, has merge conflicts, or the user asks to fix conflicts on a PR.
create-pr
Use when creating a new GitHub pull request, opening a PR for the current branch, or when another skill (like ship-it) needs a PR created for a branch that does not have one yet.