Borrowing it
Nothing to install: this file belongs to pdugan20/rewind. 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/pdugan20/rewind/main/.agents/skills/changelog-writer/SKILL.mdgit clone --depth 1 https://github.com/pdugan20/rewindWrote 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/pdugan20/rewind/changelog-writer)<a href="https://agentmods.dev/skills/pdugan20/rewind/changelog-writer"><img src="https://agentmods.dev/badge/skills/pdugan20/rewind/changelog-writer/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/pdugan20/rewind/changelog-writer"><img src="https://agentmods.dev/badge/skills/pdugan20/rewind/changelog-writer.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.00068 | $0.02058 |
| Opus 5 | $0.00034 | $0.01029 |
| Sonnet 5 | $0.00014 | $0.00412 |
| Haiku 4.5 | $0.00007 | $0.00206 |
Grade A, and why
changelog-writer 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.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changelog Writer
Writes and audits entries in docs-mintlify/changelog.mdx. Enforces a reader-facing voice modeled on Stripe, Linear, Resend, and Mintlify: short, benefit-led, concrete, no vanity.
When to use
- Adding a new entry after a release
- Auditing existing entries for consistency
- Reviewing a draft entry someone wrote for voice and length
- Cleaning up accumulated drift across the file
The core rule
Every sentence must answer: "what can a reader now do, or rely on?" If a line describes how the team built something, cut it.
Writing rules
- Length. One sentence for minor changes. Two short sentences or ≤6 bullets for major releases. Anything longer is two entries pretending to be one.
- Voice. Active, present tense, reader as subject. "You can now filter by date" or "Listening endpoints now include
apple_music_url" — not "We added date filtering" or "Date filtering has been implemented". - Benefit before mechanism. Lead with the capability. Put the tool/endpoint name second. "Full article text via new
get_articletool" — not "New Voyage AI integration enables get_article". - Concrete nouns. Name the endpoint, field, tool, or parameter explicitly (wrap in backticks). Vague ("improvements to reading") is useless.
- Link out. For anything with its own doc page, link it. Don't re-explain in the changelog.
- No emojis. No exclamation marks. Project-wide rule and matches Stripe/Linear convention.
Anti-patterns — always cut
- Version archaeology. "Rolls up v0.3.0 → v0.4.3 into one entry", "this release combines…". The date label does this work.
- Vanity metrics. Coverage percentages, "rescues NYT/Reuters", "3x faster", "now supports 12 providers". Readers don't care about the work; they care about the outcome. If a number matters (a new cap, a new limit), state it flatly — no celebration.
- Future work. "Coming soon", "planned for next release", "future: Goodreads support". Changelogs are for shipped things only. File futures in a roadmap doc.
- Implementation trivia. Embedding model names, algorithm constants (RRF k=60, cosine, 512 dim), tokenizer details, cache TTLs, internal class names (
verify_credentialsmethod), framework specifics. Exception: if a reader can pass or observe the thing, it stays. - Counting the work. "12 new tools", "10 entity resources", "3 new prompts" — numbers without named items are filler. Either name the useful ones or omit.
- Self-reference to prior entries. "As mentioned last release…", "building on the March update…". Each entry stands alone.
- Hedged language. "We've begun rolling out", "some users may see". Either it shipped or it didn't.
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 · 184 lines · 68 tokens per session scan A 13db074a2a95
changelog-writer is a skill published in the GitHub repository pdugan20/rewind (5 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 2,058 once invoked, about $0.0003 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-31.
Other skills, from other repositories
hono-cloudflare
Hono on Cloudflare Workers - bindings, KV, D1, R2, Durable Objects, and edge deployment patterns.
git-commit
Execute git commit with conventional commit message analysis, intelligent staging, and message generation. Use when user asks to commit changes, create a git commit, or mentions "/commit". Supports: (1) Auto-detecting type and scope from changes, (2) Generating conventional commit messages from diff, (3) Interactive…
cloudflare
Use when working on Cloudflare's edge platform — wrangler.jsonc bindings, choosing between D1/KV/R2/Durable Objects/Queues, deploying a Worker or SPA via Static Assets, or designing around a Workers runtime limit. NOT generic CI/release (that is deployment), NOT Next.js framework wiring (that is nextjs), NOT DNS…
git-workflow
Guided git workflows: prepare PRs, clean up branches, resolve merge conflicts, handle monorepo tags, squash-and-merge patterns. Use when asked to prepare a PR, clean branches, resolve conflicts, or tag a release.
skills-update
USE WHEN: updating locked agent skills from skills-lock.json, refreshing upstream skill content, or running npx skills update for project skills. DO NOT USE WHEN: adding new skills (use npx skills add with explicit approval), running bare npx skills update without skill names, or updating project-local skills that are…
hello-site
Reproduce a Davflare static site with existing MCP tools only (publishsite / imageupload). Use when onboarding or demoing “chat → site”.