Borrowing it
Nothing to install: this file belongs to SolaceProducts/solace-broker-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/SolaceProducts/solace-broker-mcp/main/.claude/skills/changelog/SKILL.mdgit clone --depth 1 https://github.com/SolaceProducts/solace-broker-mcpWrote 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/solaceproducts/solace-broker-mcp/changelog)<a href="https://agentmods.dev/skills/solaceproducts/solace-broker-mcp/changelog"><img src="https://agentmods.dev/badge/skills/solaceproducts/solace-broker-mcp/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/solaceproducts/solace-broker-mcp/changelog"><img src="https://agentmods.dev/badge/skills/solaceproducts/solace-broker-mcp/changelog.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00042 | $0.02075 |
| Opus 5 | $0.00021 | $0.01038 |
| Sonnet 5 | $0.00008 | $0.00415 |
| Haiku 4.5 | $0.00004 | $0.00208 |
Grade A, and why
changelog 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 — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog
Draft the [Unreleased] entry for the change on the current branch, matching the
existing voice of CHANGELOG.md. Invoked with /changelog.
The skill drafts and prints a diff; it never commits. A human reviews the entry in the PR like any other change.
When to use
- Before opening or updating a PR that changes behavior, config schema, or a tool.
- Not needed for changes with no user-visible or operator-visible surface (pure
test/refactor/docs) — those may carry a
no-changeloglabel instead.
Usage
/changelog— draft an entry for the current branch's changes/changelog <git-range>— draft for an explicit range, e.g.v0.5.0..HEADor a single ticket's commits (required when drafting frommain, which has no branch diff)
Steps
Step 1: Determine the change set and gather tickets
- On a feature branch:
git diff main...HEADfor the file changes andgit log main..HEAD --format=%s%n%bfor commit subjects/bodies — the commits are the primary source of the SOL ticket(s) and the "why." - With an explicit range argument: use it verbatim for both the diff and the log.
- If HEAD is on the default branch (
main) and no range was given: stop and ask for a range — do not diffmain...HEAD(it is empty and would silently no-op). - PR context is optional:
gh pr view --json title,body(orgh pr list --search <SOL-ticket>for a range) adds the "why." Ifghis missing, unauthenticated, or the branch has no PR, continue from git data alone. - Ticket sourcing: take
SOL-XXXXXfrom the branch name, commit subjects, or PR title. If none can be found, writeTracked under SOL-????.and flag it for the human — never invent a ticket number.
Step 2: Learn the house voice
Read CHANGELOG.md before drafting: the [Unreleased] section for what is
pending, and [0.5.0] and [0.3.0] for the structure of a breaking-change entry
and the form of a migration table. Take structure from them, not length — see the
length bullet below. Match the conventions here, do not impose a generic style:
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 Changed · +30 lines a08386e39c3c
- 12d ago First seen · 126 lines · 42 tokens per session scan A 6a85cda9bc6b
changelog is a skill published in the GitHub repository SolaceProducts/solace-broker-mcp (11 stars, last pushed today), licensed Apache-2.0. It adds 42 tokens to every session and 2,075 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-30.
Other skills, from other repositories
conventional-git
Conventional Commits v1.0.0 branch naming and commit message standards for GitHub and GitLab projects. Use when creating branches, writing commits, generating commit messages, reviewing branch conventions, or setting up changelog automation. Apply when your project needs consistent git history, SemVer-driven releases…
octocat
Handles git and GitHub operations using the gh CLI. Use when the user asks about pull requests (PRs), GitHub issues, repo management, branching, merging, rebasing, cherry-picking, merge conflict resolution, commit history cleanup, pre-commit hook debugging, GitHub Actions workflows, or releases. Covers creating and…
agent-release-swarm
Agent skill for release-swarm - invoke with $agent-release-swarm.
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.