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 Dragoon0x/everything-design-taste --skill changelog-writinggit clone --depth 1 https://github.com/Dragoon0x/everything-design-tasteWrote 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/dragoon0x/everything-design-taste/changelog-writing)<a href="https://agentmods.dev/skills/dragoon0x/everything-design-taste/changelog-writing"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/changelog-writing/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/dragoon0x/everything-design-taste/changelog-writing"><img src="https://agentmods.dev/badge/skills/dragoon0x/everything-design-taste/changelog-writing.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.00020 | $0.00249 |
| Opus 5 | $0.00010 | $0.00125 |
| Sonnet 5 | $0.00004 | $0.00050 |
| Haiku 4.5 | $0.00002 | $0.00025 |
Grade A, and why
changelog-writing 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 7d 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.
What it actually says
Changelog Writing
Changelog Format
User-Facing
- Lead with benefit: "You can now export to PDF" not "Added PDF export module."
- Group: New, Improved, Fixed.
- Skip internal changes users don't care about.
- Link to docs for new features.
Developer-Facing
- Follow Keep a Changelog format.
- Group: Added, Changed, Deprecated, Removed, Fixed, Security.
- Reference issue/PR numbers.
- Highlight breaking changes prominently.
Semantic Versioning Communication
- Major (2.0): "Big update" — migration guide required.
- Minor (1.5): "New features" — backwards compatible.
- Patch (1.5.1): "Bug fixes" — no new features.
Anti-Patterns
- "Various bug fixes and performance improvements" — be specific.
- Technical jargon in user-facing notes.
- No date on entries.
- Changelog that's just git commit messages.
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.
- 7d ago First seen · 32 lines · 20 tokens per session scan A 8df823f329bd
changelog-writing is a skill published in the GitHub repository Dragoon0x/everything-design-taste (11 stars, last pushed 5mo ago), licensed MIT. It adds 20 tokens to every session and 249 once invoked, about $0.0001 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-09-03.
Other skills, from other repositories
re0-release
Walk a pending change through this repo's shipping and releasing checklist end to end, then tag and publish once confirmed. User-invoked: run it when you've decided to ship.
goshipit
Pre-launch codebase audit skill. Use this whenever someone is about to ship, deploy, launch, push to main/prod, or merge a release - even without "goshipit" explicitly. Trigger on: "is my app ready?", "can I deploy now?", "pre-deploy check", "review before launch", "is this production-ready?", "check my codebase"…
release-readiness
The go/no-go gate before shipping — a structured launch checklist across security, data, legal, operations, performance, accessibility and rollback, producing an explicit ship or do-not-ship decision with named blockers. Use when the user says "ready to launch", "go live", "ship it", "pre-launch", "launch checklist"…
land
Post-merge sanity check. Verifies branch, HEAD sha, that local matches remote, and that the working tree is clean. dragoon does NOT trigger deploys (platform-specific creds out of scope). Use right before a deploy step in CI or before manual prod pushes. Exits non-zero if any check fails. Run as node…
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.