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 commands/nickveenhof/cursor-gitlab-plugin/pipeline-statusgit 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.00014 | $0.00184 |
| Opus 5 | $0.00007 | $0.00092 |
| Sonnet 5 | $0.00003 | $0.00037 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
pipeline-status 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.
What it actually says
Pipeline status
- Ask the user for the project path. If the user asks about "my pipelines" or "my branch", ask for their GitLab username or the specific branch name.
- Use
manage_pipelinewithlist=trueto fetch recent pipelines. - Summarize pipeline statuses (passed, failed, running, pending).
- For any failed pipeline, use
get_pipeline_jobsto list jobs and identify failures. - Offer to retry failed pipelines using
manage_pipelinewithretry=true. - For root-cause diagnosis and automated fixes beyond retrying, suggest the Fix CI/CD Pipeline Flow in GitLab's Duo Agent Platform.
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 · 14 lines · 14 tokens per session scan A ce5bbe328182
pipeline-status is a command published in the GitHub repository nickveenhof/cursor-gitlab-plugin (3 stars, last pushed 5mo ago), licensed MIT. It adds 14 tokens to every session and 184 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 commands, from other repositories
monitor-ci
Monitors pull request CI checks until they are resolved (pass or fail).
monitor-ci
You are the orchestrator for monitoring Nx Cloud CI pipeline executions and handling self-healing fixes. You spawn the ci-monitor-subagent subagent to poll CI status and make decisions based on the results.
actions
Command "actions" from openclaw/crabbox, covering actions, subcommands, hydrate, register and dispatch.
ci-health
Check all GitHub Actions workflows for failures, create P0 tickets, gate each ticket, and auto-fix safe failures.
cf-scaffold-project
Scaffold a Cloudflare project — Worker, Pages, or Worker+D1+R2 starter — with Wrangler config, Terraform skeleton, and GitHub Actions deploy using scoped API tokens.
status
Check what's actually running: Railway control plane + deep health + logs + CI. Usage: /status [prod|dev] [--quick].