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/jmrplens/gitlab-mcp-server/generate-release-notesnpx skills add jmrplens/gitlab-mcp-server --skill generate-release-notesgit clone --depth 1 https://github.com/jmrplens/gitlab-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/jmrplens/gitlab-mcp-server/generate-release-notes)<a href="https://agentmods.dev/skills/jmrplens/gitlab-mcp-server/generate-release-notes"><img src="https://agentmods.dev/badge/skills/jmrplens/gitlab-mcp-server/generate-release-notes.svg" alt="Measured on agentmods" height="20"></a>What 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.00067 | $0.01320 |
| Opus 5 | $0.00034 | $0.00660 |
| Sonnet 5 | $0.00013 | $0.00264 |
| Haiku 4.5 | $0.00007 | $0.00132 |
Grade A, and why
generate-release-notes 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Generate Release Notes
Overview
Generate polished, categorized release notes for a GitLab project by comparing two Git refs. This skill orchestrates multiple MCP tools to gather commits, merged merge requests, and diffs, then produces human-readable release notes.
When to Use
- Creating release notes for a new tag or version
- Summarizing changes between any two Git references (tags, branches, SHAs)
- Preparing changelog entries for a release
- Reviewing what changed between deployments
Prerequisites
- A GitLab project accessible via the MCP server
- Two valid Git refs (tags, branches, or commit SHAs) to compare
Workflow
Step 1: Identify the Project and Refs
Determine the project ID (or namespace/project path) and the two refs to compare.
Common patterns:
- Tag to tag:
v1.0.0→v1.1.0 - Tag to branch:
v1.0.0→main - Branch to branch:
release/1.0→release/1.1 - Commit to tag:
abc1234→v1.1.0
Step 2: Gather Data (Choose One Approach)
Approach A: Manual Orchestration (Recommended)
Orchestrate the tools manually and categorize the results yourself:
-
Compare refs to get commits and diffs:
Use gitlab_repository with action "compare": - project_id: <project_id> - from: <base_ref> - to: <target_ref> -
Search for merged MRs in the change range:
Use gitlab_merge_request with action "list": - project_id: <project_id> - state: "merged" - per_page: 100 -
Correlate commits with MRs to enrich the data.
-
Categorize changes based on MR labels, commit prefixes, and descriptions.
Approach B: Use the MCP Prompt
For a prompt-based approach that provides enriched context to the LLM:
Use the generate_release_notes prompt with:
- project_id: <project_id>
- from: <base_ref>
- to: <target_ref>
Step 3: Format the Release Notes
Organize changes into these categories (skip empty categories):
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.
- 4d ago First seen · 170 lines · 67 tokens per session scan A b2f9d06ef854
generate-release-notes is a skill published in the GitHub repository jmrplens/gitlab-mcp-server (31 stars, last pushed 4d ago), licensed MIT. It adds 67 tokens to every session and 1,320 once invoked, about $0.0003 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-30.
Other skills, from other repositories
push-release
Push to GitHub and optionally bump version to trigger PyPI release.
release
Automate the full release workflow for syllago. USE WHEN creating a release OR tagging a version OR bumping VERSION OR publishing to GitHub releases.
hmem-release
Pre-publish checklist for hmem: skills synced, version bumped, tests green, nothing forgotten. Use before npm publish or when the user says 'release', 'publish', 'push a release', or 'neue Version'.
open-source
Documentation reference for writing Python code using the browser-use open-source library. Use this skill whenever the user needs help with Agent, Browser, or Tools configuration, is writing code that imports from browseruse, asks about @sandbox deployment, supported LLM models, Actor API, custom tools, lifecycle…
kayba-stage-5-action-plan
Triage each insight into discard/code-fix/prompt-fix and produce a prioritized action plan with specific recommendations. Trigger when the user says "run stage 5", "make action plan", "triage skills", or when invoked by the kayba-pipeline orchestrator. Requires eval outputs from stages 1-4.
kayba-stage-2-domain-context
Gather domain context about the repository and agent — system prompt, tool definitions, domain docs, and behavior patterns from traces. Trigger when the user says "run stage 2", "gather context", "domain context", or when invoked by the kayba-pipeline orchestrator.