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/create-merge-requestgit 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.00020 | $0.00209 |
| Opus 5 | $0.00010 | $0.00105 |
| Sonnet 5 | $0.00004 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
Grade A, and why
create-merge-request 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
Create merge request
- Determine the current branch name and the default target branch.
- Ask the user for a merge request title. Suggest a conventional commit format (
feat:,fix:,chore:, etc.) per the gitlab-workflow rule. - Ask for a description. Remind the user to reference related issues with
#<issue-number>. - Use
search_labelsto show available labels and let the user pick relevant ones. - Optionally ask about milestone, assignees, and reviewers. If the user wants to assign themselves or add themselves as a reviewer, ask for their GitLab username.
- Use the GitLab MCP
create_merge_requesttool with the project path, source branch, target branch, title, description, labels, milestone, assignees, and reviewers. - Report the resulting merge request URL.
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 · 15 lines · 20 tokens per session scan A 676f487afc68
create-merge-request is a command published in the GitHub repository nickveenhof/cursor-gitlab-plugin (3 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 209 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
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.