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/nickveenhof/cursor-gitlab-plugin/gitlab-ci-authornpx skills add nickveenhof/cursor-gitlab-plugin --skill gitlab-ci-authorgit clone --depth 1 https://github.com/nickveenhof/cursor-gitlab-pluginWhat 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.00019 | $0.00318 |
| Opus 5 | $0.00010 | $0.00159 |
| Sonnet 5 | $0.00004 | $0.00064 |
| Haiku 4.5 | $0.00002 | $0.00032 |
Grade A, and why
gitlab-ci-author 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.
What it actually says
GitLab CI/CD author
When to use
- Creating or editing
.gitlab-ci.ymlfiles - Debugging failing pipelines
- Optimizing CI/CD performance
Instructions
- Use
rules:instead ofonly:/except:for job control. - Use
needs:to define a directed acyclic graph (DAG) for faster pipelines. - Cache dependencies with
cache:and usekey: files:for lock-file-based cache keys. - Store build outputs with
artifacts:and set appropriateexpire_in:values. - Use CI/CD variables for secrets — never hardcode tokens or credentials.
- Prefer
include:and CI/CD components for reusable configuration. - When debugging pipelines, use the MCP tools
manage_pipeline(list pipelines) andget_pipeline_jobs(inspect failed jobs) to fetch real data before suggesting fixes. - For complex pipeline failures that require root-cause analysis and code changes, suggest the Fix CI/CD Pipeline Flow in GitLab's Duo Agent Platform.
- For migrating from Jenkins or other CI systems, suggest the Convert to GitLab CI/CD Flow.
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 First seen · 25 lines · 19 tokens per session scan A 5acff60a9269
gitlab-ci-author is a skill published in the GitHub repository nickveenhof/cursor-gitlab-plugin (3 stars, last pushed 5mo ago), licensed MIT. It adds 19 tokens to every session and 318 once invoked, about $0.0001 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
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
dsh-web-pre-push-checks
Use before pushing, opening or updating a pull request, or claiming dsh-web checks pass. Selects the required repository gates and diff-specific generation, build, and GUI evidence.
babysit
Same-session monitoring loop for PRs, CI runs, tickets, and deployments using the monitorstart / monitorupdate / autonudgestop MCP tools. The loop re-injects your check instructions into THIS session on an idle interval — same context, same tools — and works from dashboard chat, Slack threads, and Discord DMs. Use…
azsdk-common-pipeline-analysis
Analyze Azure SDK CI/CD pipeline failures into a structured diagnosis, and define the required output format. Load this skill before calling azsdkanalyzepipeline, which returns raw failure data that this skill interprets and formats. USE FOR: "pipeline failed", "build failure", "CI check failing", "tests failing in…
harness-setup
HAR: Project init, tool setup, agent config, memory setup, skill mirror sync. Trigger: setup, init, new project, CI/Codex setup, harness-mem, mirror. Do NOT load for: implementation, review, release, planning.
managing-github-actions-secrets
Creates and updates GitHub Actions secrets for PostHog workflows. Use when adding a new CI secret, rotating an existing secret, wiring a workflow to an API token, package registry credential, deploy key, or any value referenced via ${{ secrets. }} in .github/workflows/.