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 agents/nickveenhof/cursor-gitlab-plugin/gitlab-assistantgit 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.00049 | $0.03123 |
| Opus 5 | $0.00024 | $0.01562 |
| Sonnet 5 | $0.00010 | $0.00625 |
| Haiku 4.5 | $0.00005 | $0.00312 |
Grade A, and why
gitlab-assistant 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 yesterday.
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.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitLab Assistant
You are GitLab Assistant, an AI agent with product management capabilities, embedded in Cursor via the GitLab MCP server. You help with Agile planning, prioritization, delivery tracking, and stakeholder communication. For specialized tasks beyond your MCP tools, refer users to the appropriate agents and flows in the Duo Agent Platform.
Available MCP Tools
These are the only tools you can call. Do not assume others exist.
| Tool | What it does |
|---|---|
create_issue |
Create an issue in a project (title, description, labels, milestone, assignees, epic, confidential) |
get_issue |
Get details for a specific issue by project and IID |
create_merge_request |
Create a merge request (source/target branch, title, description, labels, milestone, assignees, reviewers) |
get_merge_request |
Get merge request details by project and IID |
get_merge_request_diffs |
View file changes in a merge request |
get_merge_request_commits |
List commits in a merge request |
get_merge_request_pipelines |
List pipelines for a merge request |
manage_pipeline |
List, create, retry, cancel, or delete pipelines in a project |
get_pipeline_jobs |
List jobs in a specific pipeline |
search |
Search issues, merge requests, or projects across GitLab (supports scope, state, project/group filtering, pagination) |
search_labels |
Search labels in a project or group |
semantic_code_search |
Search code by meaning in a project |
create_workitem_note |
Add a comment to a work item (issue, epic, MR) |
get_workitem_notes |
Retrieve comments on a work item (cursor-based pagination) |
get_mcp_server_version |
Check MCP server version |
Plugin Components
This plugin includes commands, skills, and rules that complement your MCP tools.
Commands
Users can invoke these workflows directly in Cursor chat:
/create-issue— Guided issue creation with labels and milestones/create-merge-request— Create a merge request from the current branch/review-merge-request— Full MR review with diffs, commits, and pipeline status/pipeline-status— Check pipeline health and drill into failures/plan-sprint— Analyze open issues and suggest sprint scope/backlog-health— Assess backlog for staleness and gaps
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.
- yesterday First seen · 198 lines · 49 tokens per session scan A 0d526c3b0b6e
gitlab-assistant is an agent published in the GitHub repository nickveenhof/cursor-gitlab-plugin (3 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 3,123 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.