datapages: Skill for Claude Code

.claude/skills/changelog/SKILL.md

changelog is a skill for Claude Code from romshark/datapages. It costs 28 tokens per session (550 once invoked), scanned A, original, MIT.

A guide for maintaining a CHANGELOG.md file and preparing software releases. A changelog is a user-facing record of added, changed, fixed, removed, deprecated, and security-related changes.

In plain words
What is it for?
Use it to add user-visible changes under Unreleased, write security and breaking-change notes, or prepare a versioned release.
Why use it?
It prevents release notes from being missing, misplaced, or too vague for users to understand whether they are affected. It also standardizes version headings, comparison links, and release tags.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is romshark/datapages's own configuration. It tells Claude Code how to work on datapages itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything datapages configures →

Reuse

Borrowing it

Nothing to install: this file belongs to romshark/datapages. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/romshark/datapages/main/.claude/skills/changelog/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/romshark/datapages

Made for: Claude Code.

Wrote 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.

agentmods badge for changelog

README.md
[![agentmods](https://agentmods.dev/badge/skills/romshark/datapages/changelog/github.svg)](https://agentmods.dev/skills/romshark/datapages/changelog)
Your own site
<a href="https://agentmods.dev/skills/romshark/datapages/changelog"><img src="https://agentmods.dev/badge/skills/romshark/datapages/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.

agentmods 80×15 button for changelog

Your own site · 80×15
<a href="https://agentmods.dev/skills/romshark/datapages/changelog"><img src="https://agentmods.dev/badge/skills/romshark/datapages/changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 28 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 550 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00028 $0.00550
Opus 5.5 $0.00011 $0.00220
Sonnet 5.5 $0.00006 $0.00110
Haiku 4.5 $0.00003 $0.00055

Measured 1mo ago against content hash 09db45348416, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.claude/skills/changelog/SKILL.md · 29 lines

What it actually says

CHANGELOG.md follows Keep a Changelog. The release workflow publishes each tag's section and fails when it's missing. TestChangelogReleases validates version headings.

  • Add user-visible framework, CLI and generated-code changes under ## [Unreleased] in the same commit. Omit docs, test, chore and ci.
  • Sort entries into Added, Changed, Deprecated, Removed, Fixed and Security.
  • Within a section, group entries under #### subheadings by where the change applies, in this order: `datapages lint` and `datapages gen` for what the app model may contain and what is reported about it; Generated code, opened by the line "Run datapages gen to apply these."; Runtime and modules for what applies on upgrade alone; `datapages init` for the files it writes. Leave out a subheading with no entries.
  • Don't repeat in an entry what its subheading says: no "in datapages lint and datapages gen" and no closing "Run datapages gen."
  • Use imperative entries like commit titles: Reject subject fields tagged json:"-". Say enough for users to determine whether they are affected.
  • A Security entry follows Security entries.
  • A breaking change repeats the migration steps of its BREAKING: block.
  • Do not add a separate entry for a runtime/ API change. The entry for the user-visible change that requires it goes under Generated code.
  • To release, rename ## [Unreleased] to ## [X.Y.Z] - YYYY-MM-DD, insert an empty ## [Unreleased], update the compare links and tag vX.Y.Z.

Security entries

A security entry lets users determine exposure and remediation:

  • State who can read or do what to whom: "any signed-in user can read another user's private events", not "a privacy issue".
  • Describe affected applications with terms users can find in their code.
  • Give exact affected versions, verified against the release history.
  • Give upgrade, regeneration and redeploy steps. Include a workaround or say there is none.
  • Link the GHSA or CVE when one exists.

Leave severity labels, CVSS scores and exploit steps to the advisory.

Changes

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.

  1. 1mo ago Changed · +2 lines 09db45348416
  2. 1mo ago First seen · 27 lines · 28 tokens per session scan A f2e9c669ae50

Subscribe to this mod's changes

changelog is a skill published in the GitHub repository romshark/datapages (119 stars, last pushed 2d ago), licensed MIT. It adds 28 tokens to every session and 550 once invoked, about $0.0001 per session on Opus 5.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-09-27.

Related

changelog compared with skills from other repositories

changelog next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
changelogromshark/datapagesSkill1192d agoMITA28Claude Code
releasejrswab/axeSkill90915d agoApache-2.0A30Claude Code, Codex
Release Notes GeneratorAgentEra/AgentlySkill1.7k24d agoApache-2.0A46Claude Code, Codex
pinned-release-checklistAgentEra/AgentlySkill1.7k24d agoApache-2.0A18Claude Code, Codex
Release Readiness ReviewerAgentEra/AgentlySkill1.7k24d agoApache-2.0A18Claude Code, Codex
Release ChecklistAgentEra/AgentlySkill1.7k24d agoApache-2.0A19Claude Code, Codex
crawlkitvincentkoc/dotskillsSkill111yesterdayMITA30Codex