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 skills add Jamie-BitFlight/claude_skills --skill create-merge-request-changeloggit clone --depth 1 https://github.com/Jamie-BitFlight/claude_skillsWrote 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/jamie-bitflight/claude_skills/create-merge-request-changelog)<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/create-merge-request-changelog"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/create-merge-request-changelog/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/jamie-bitflight/claude_skills/create-merge-request-changelog"><img src="https://agentmods.dev/badge/skills/jamie-bitflight/claude_skills/create-merge-request-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 336 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 334 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
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.1 | $0.00090 | $0.03994 |
| Opus 5 | $0.00045 | $0.01997 |
| Sonnet 5 | $0.00018 | $0.00799 |
| Haiku 4.5 | $0.00009 | $0.00399 |
Grade A, and why
create-merge-request-changelog scanned grade A with 1 finding 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 11d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **Authentication API documentation with examples**: Complete API docs with curl examples and error codes How it starts
The opening of the file, as written. The whole thing — 548 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Merge Request Changelog
Generate comprehensive, business-focused merge request descriptions by analyzing git changes. This skill adapts the structured analysis approach from JIRA release notes to work purely with git data.
Quick Start
# Analyze current branch against main
/create-merge-request-changelog
# Analyze specific branch
/create-merge-request-changelog feature/new-auth
# Analyze specific branch against custom target
/create-merge-request-changelog feature/new-auth develop
# Analyze specific commit range
/create-merge-request-changelog abc123f def456g
Workflow
Option A: From Git Branch (Most Common)
Step 1: Extract Git Data
Run the Python CLI to gather commits, diffs, and statistics:
uv run scripts/analyze_git_changes.py [base_ref] [head_ref] --output-dir /tmp/mr-analysis
Examples:
# Current branch vs main (default)
uv run scripts/analyze_git_changes.py
# Specific branch vs develop
uv run scripts/analyze_git_changes.py develop feature/new-auth
# Specific commit range
uv run scripts/analyze_git_changes.py abc123f def456g
# Custom output directory
uv run scripts/analyze_git_changes.py main HEAD --output-dir ./analysis-output
Output files created:
commits_oneline.txt- Concise commit listcommits_detailed.txt- Full commit messages with metadatachanges.diff- Complete unified diffchanges_stat.txt- Diffstat summarychanged_files.txt- File list with change status (A/M/D)changes_numstat.txt- Per-file line changessummary.json- Machine-readable statistics
Option B: From Existing GitLab MR
Step 1: Fetch MR Data
Use the GitLab CLI integration to fetch existing MR data:
uv run scripts/fetch_gitlab_mr.py <mr-id> --output /tmp/mr-data.json
Examples:
# By MR ID
uv run scripts/fetch_gitlab_mr.py 123
# By !notation
uv run scripts/fetch_gitlab_mr.py !123
# By full URL
uv run scripts/fetch_gitlab_mr.py https://gitlab.com/org/project/-/merge_requests/123
# Without diff (faster)
uv run scripts/fetch_gitlab_mr.py 123 --no-diff
# Custom output file
uv run scripts/fetch_gitlab_mr.py 123 --output ./mr-metadata.json
What ships with it
6 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 11d ago First seen · 548 lines · 90 tokens per session scan A bbef07d2c978
create-merge-request-changelog is a skill published in the GitHub repository Jamie-BitFlight/claude_skills (66 stars, last pushed today), licensed MIT. It adds 90 tokens to every session and 3,994 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
git-commit
Generate well-formatted git commit messages following conventional commit standards.
repo-sync
Manage repo-sync on macOS for shared documents and team context. Use when asked what repo-sync does, to automatically sync a repo, add a repo to repo-sync, stop syncing or un-sync a repo, check sync health, configure repo-sync, uninstall it, or install and maintain its bundled agent skill. Ordinary one-time Git pulls…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
contributing
How to contribute to evlog, covering commit and PR conventions, changesets, the Definition of Done, testing rules, and the authored skills that walk through building a new adapter, enricher, framework integration, or map rule. Load this for any question about contributing, opening a PR, or adding something to the…
strict-tdd
Strict RED->GREEN->REFACTOR test-driven development with enforcement. Never write production code before a failing test. Atomic commits per TDD cycle.