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 Grinv/steam-games-mcp --skill changelog-stylegit clone --depth 1 https://github.com/Grinv/steam-games-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/grinv/steam-games-mcp/changelog-style)<a href="https://agentmods.dev/skills/grinv/steam-games-mcp/changelog-style"><img src="https://agentmods.dev/badge/skills/grinv/steam-games-mcp/changelog-style/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/grinv/steam-games-mcp/changelog-style"><img src="https://agentmods.dev/badge/skills/grinv/steam-games-mcp/changelog-style.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.00050 | $0.01513 |
| Opus 5 | $0.00025 | $0.00757 |
| Sonnet 5 | $0.00010 | $0.00303 |
| Haiku 4.5 | $0.00005 | $0.00151 |
Grade A, and why
changelog-style 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 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.
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.
This is a copy
94% identical to changelog-style — 7 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog entries: style & workflow
Entries in CHANGELOG.md should be short and self-describing. Style reference:
common-changelog. The workflow
below (how to actually produce those entries from commit history) is
synthesized from three changelog-generation agent skills:
GoogleChromeLabs/changelog-generation-skill,
ComposioHQ/awesome-claude-skills/changelog-generator,
and glincker/changelog-generator.
Style
- One line per entry — two only if it genuinely needs a "why". Common-changelog is stricter here ("a change should be brief and to the point, no more than one line long"); we allow a second line for a real rationale. Skip mechanism/implementation detail; that belongs in the commit message or PR description, not the changelog. Concrete gut-check: after writing an entry, measure the prose (excluding the trailing link) — past ~150 chars you're burying the fact, not stating it; reread it and cut, don't just eyeball "does this look like one line" (a long single physical line with no embedded newline still fails this rule even though it dodges the separate "no dangling link" issue below) — e.g. generalize the affected set instead of enumerating every affected tool/field by name (past 2-3 names, say "a keyless Web API tool" rather than listing all seven).
- Imperative, present tense: "Add X", "Fix Y" — not "Added X" / "Fixed Y".
- Self-describing: a reader skimming just the bullet — without its
### Added/### Fixedcategory heading for context — should still understand the change and its effect. - Exclude dev-only/maintenance changes: dotfile tweaks, dev-dependency bumps, test-only changes, pure code-style edits — these are not interesting to someone consuming the released package, so they don't get an entry; put them in the commit message instead. Exception: a refactor that could have user-visible side effects (behavior change, perf, a fixed edge case) still gets an entry describing that effect, not the refactor itself.
- Link commits/PRs/issues: reference the commit that made the change, and
the PR or issue too when one exists. Exception: a version whose entire
content is one single commit — don't repeat the identical link after every
bullet; put one link at the section level instead (e.g. "Everything below
is one commit:
[<sha>](...)." right under the version heading). - No dangling link line: keep an entry and its link(s) on one physical source line, even if long. GitHub renders a single soft-wrapped newline inside a list item as a real line break, so a wrapped entry shows its link stranded alone on the next line instead of reading as one continuous bullet.
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 · 102 lines · 50 tokens per session scan A f3e06683cbd3
changelog-style is a skill published in the GitHub repository Grinv/steam-games-mcp (4 stars, last pushed 17d ago), licensed MIT. It adds 50 tokens to every session and 1,513 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 94% identical to changelog-style, differing in 7 lines, and is treated as a copy.
Other skills, from other repositories
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'.
publish-release
Releases a new McpOrchestrator version end to end — version bump PR, tag, and the automated deploy to GitHub Releases, NuGet, and the MCP Registry. Use when asked to release, publish, deploy, ship, or bump the version of McpOrchestrator.
release-notes
Writes user-facing release notes from a git commit range. Use when asked to draft release notes, a changelog entry, or "what's new" text for a release.
release-and-publish
Ship a release end-to-end across every registry the project targets (npm, MCP Registry, GitHub Releases for .mcpb bundles, GHCR). Runs the final verification gate, fast-forwards main when the release rode a release PR, creates the annotated tag on the commit main now points at, pushes commits and tags, then publishes…
git-wrapup
Land working-tree changes as logical commits — the work grouped by concern, topped by a release commit (version bump, changelog, regenerated artifacts). Verify, commit. Stops at "committed locally on main" — or, when the project releases through a release PR, at "release branch pushed, PR open". No tag, no push to…
release-pr-review
Review pass on an open release PR (release/ → main) — the step between git-wrapup and release-and-publish when a project releases in gated release PR mode. Reads the PR's commit range through the code-simplifier lens plus a correctness review, verifies whatever an automated reviewer left on the PR, lands fixes as…