changelog-and-docs

changelog-and-docs is a skill for Claude Code from nirholas/three.ws. It costs 42 tokens per session (1,465 once invoked), scanned A, original, Apache-2.0.

A set of rules for documenting software changes and publishing user-visible release notes. It explains when to update the changelog, which labels to use, and how the site regenerates its Markdown, JSON, XML, and community feeds.

In plain words
What is it for?
Use it when adding features, fixes, security work, SDK releases, documentation, or new pages that need to appear in the public changelog.
Why use it?
It prevents changes from being shipped without understandable documentation or a changelog entry. It also catches malformed changelog data during the build.

Skill for Claude Code

Written for Claude Code: when-to-use in frontmatter.

Good fit Use it when adding features, fixes, security work, SDK releases, documentation, or new pages that need to appear in the public changelog.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nirholas/three.ws/changelog-and-docs
Install

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.

Any agent
npx skills add nirholas/three.ws --skill changelog-and-docs
Clone the repo
git clone --depth 1 https://github.com/nirholas/three.ws

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-and-docs

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/nirholas/three.ws/changelog-and-docs"><img src="https://agentmods.dev/badge/skills/nirholas/three.ws/changelog-and-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 42 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,465 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.00042 $0.01465
Opus 5.5 $0.00017 $0.00586
Sonnet 5.5 $0.00008 $0.00293
Haiku 4.5 $0.00004 $0.00146

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

Security

Grade A, and why

changelog-and-docs 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-and-docs/SKILL.md · 39 lines

How it starts

The opening of the file, as written. The whole thing — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Changelog: every user-visible change gets an entry

The three.ws community follows the public changelog (three.ws/changelog, RSS, JSON, Telegram). Keep it alive:

  • New page? Nothing extra: the added date in data/pages.json feeds the changelog automatically.
  • Everything else users would notice (feature, improvement, fix, SDK release, security work): append an entry to data/changelog.json with date, community-readable title + summary (plain language, no commit jargon), and tags from: feature, improvement, fix, sdk, infra, docs, security. Optional link must be a live page path.
  • npm run build:pages regenerates CHANGELOG.md, public/changelog.json, and public/changelog.xml. It also validates your entry and fails the build on a malformed one.
  • Delivery to the community is automatic. /api/cron/changelog-push (Cloud Scheduler, every 20 min) reads the feed baked into the running image, diffs it against DB state (app_settings), and posts anything new to two lanes: the community Telegram channel (TELEGRAM_CHANGELOG_CHAT_ID, @three_ws) gets every entry, and a reply thread on @trythreews (pushXLane) gets every entry that passes data/changelog-x-filter.json. That filter keeps a public, unattended feed free of wallet and payment internals, keys, outages, security work, other coins, and bare fixes; extend it there, with a reason, rather than in code. X was retired on 2026-07-18 and turned back on by the owner on 2026-09-24. The three reviewed feature posts a day are a separate pipeline (docs/x-content-pipeline.md). An entry goes out on its own shortly after the deploy that ships it; there is no manual push step. Credentials live on the Cloud Run service. Do NOT run npm run changelog:push / changelog:push:x for routine releases anymore: their file-based state (data/changelog-*-state.json) is separate from the cron's DB state, so a manual push double-posts. The scripts remain for --dry-run previews and owner-directed backfills only.
  • Internal-only chores (CI, lockfiles, refactors with no visible effect) do NOT get entries.

Read the full file on GitHub · 39 lines

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 First seen · 39 lines · 42 tokens per session scan A 1127b8dc31ce

Subscribe to this mod's changes

changelog-and-docs is a skill published in the GitHub repository nirholas/three.ws (280 stars, last pushed yesterday), licensed Apache-2.0. It adds 42 tokens to every session and 1,465 once invoked, about $0.0002 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-10-11.

Related

changelog-and-docs compared with skills from other repositories

changelog-and-docs next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
changelog-and-docsnirholas/three.wsSkill280yesterdayApache-2.0A42Claude Code
release-changelog-harnessArenukvern/mcp_flutterSkill398todayMITA84Claude Code
changelog-notesmatebenyovszky/agentplaybooksSkill11yesterdayMITA35Claude Code, Codex
metagit-release-auditmetagit-ai/metagit-cliSkill411d agoMITA59Claude Code, Codex
git-wrapupcyanheads/pubmed-mcp-serverSkill168yesterdayApache-2.0A109Claude Code
release-pr-reviewcyanheads/ntfy-mcp-serverSkill25yesterdayApache-2.0A136Claude Code
git-wrapupcyanheads/openalex-mcp-serverSkill182d agoApache-2.0A109Claude Code