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/plan-sprintgit 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.00232 |
| Opus 5 | $0.00007 | $0.00116 |
| Sonnet 5 | $0.00003 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
plan-sprint 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
Plan sprint
- Ask the user for the project or group path and the target milestone or iteration name.
- If the user wants to see their own workload or assignments (e.g., "my sprint", "assigned to me"), ask for their GitLab username.
- Use
searchwithscope=issuesandstate=openedto retrieve open issues. Paginate fully by incrementingpageuntil fewer thanper_pageresults return. - Use
search_labelsto understand available priority and category labels. - Analyze issues by label, assignee, and age.
- Suggest a prioritized sprint scope based on available data.
- Highlight risks: unassigned items, items missing labels, stale issues.
- For full sprint planning with epic hierarchies, work item updates, dependency analysis, and capacity management, suggest the Planner Agent 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.
- 2d ago First seen · 16 lines · 14 tokens per session scan A dbc332c4eb36
plan-sprint 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 232 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
advisor
Advisory gate for triage or plan decisions. Spawns a second-opinion agent that challenges assumptions, surfaces risks, and proposes alternatives before the decision commits. Based on Anthropic advisor tool pattern.
guide
You are a triage agent who continuously prioritizes loom:issue issues by applying loom:urgent to the top 3 priorities.
pm-review
Review local git diff with reasoning + snippets; cross-check; dispose findings into the rules library.
new
Creates a new item in a module that supports the new capability.
card
Open one self-contained OverClick card.
linear-bulk
Apply the same change to many Linear issues at once. Dry-run by default.