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 segunadebayo/design-eng-skills --skill changeset-writinggit clone --depth 1 https://github.com/segunadebayo/design-eng-skillsWrote 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/segunadebayo/design-eng-skills/changeset-writing)<a href="https://agentmods.dev/skills/segunadebayo/design-eng-skills/changeset-writing"><img src="https://agentmods.dev/badge/skills/segunadebayo/design-eng-skills/changeset-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/segunadebayo/design-eng-skills/changeset-writing"><img src="https://agentmods.dev/badge/skills/segunadebayo/design-eng-skills/changeset-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.00048 | $0.00721 |
| Opus 5 | $0.00024 | $0.00360 |
| Sonnet 5 | $0.00010 | $0.00144 |
| Haiku 4.5 | $0.00005 | $0.00072 |
Grade A, and why
changeset-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 12d 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 — 37 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Changeset Writing
A changeset is a written intent to change, created while the change is fresh, versioned and merged into CHANGELOG.md later. Write it for the consumer reading the changelog after an upgrade, not for yourself reading the diff today.
0. Check what this repo already does
Look for an existing convention before applying this skill's defaults: a header in CHANGELOG.md declaring a format (Keep a Changelog, Common Changelog), an internal style guide, or just the shape of recent real entries. Match it. Only fall back to this skill's own defaults, described in references/CATEGORIZATION.md, if nothing exists yet.
1. Decide if this needs a changeset at all
Not every change does. Internal refactors, CI tweaks, dependency bumps with no observable effect, and doc-only changes don't need one. If a consumer would never notice or care, skip it. If you're unsure whether it's user-facing, that uncertainty is itself a sign to go check, not to default to writing one anyway.
2. Pick the semver bump
Patch, minor, or major, this is a judgment call with real edge cases: dependency-only bumps, experimental APIs, deprecations that don't remove anything yet, monorepo packages that only re-export another package's change. Full decision tree in references/BUMP-DECISIONS.md.
3. Write WHAT, WHY, and HOW
Three things, in order, every time: what changed, why a consumer should care, and (if it's not obvious) how they should react. Lead with a verb, imperative mood (Add, Fix, Remove, not Added, Fixed, Removed), name the exact API in backticks. Skip WHY and HOW when the WHAT is self-evident, don't pad a one-line fix into three sentences it doesn't need.
4. Flag breaking changes on purpose
A breaking change is not a bigger version of a normal entry, it's a different shape: what broke, why, and the exact migration step, not just a warning that something changed. Full template and real examples in references/BREAKING-CHANGES.md.
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 37 lines · 48 tokens per session scan A a8a9fb1d9532
changeset-writing is a skill published in the GitHub repository segunadebayo/design-eng-skills (6 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 721 once invoked, about $0.0002 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
omh-deploy-and-monitor
This is a Hermes-native deploy-and-monitor workflow skill.
release-core-test
Invoke when dev-testing a Cyrus change that spans CYPACK (edgeworker + CLI) and CYHOST (Vercel-hosted GUI) and the hosted GUI needs to point at an unreleased cyrus-core from this repo. Publishes cyrus-core (and claude-runner if needed) as a -test.N prerelease under the npm test dist-tag so CYHOST can install it via…
verify-and-ship
Run all quality checks (tests, lint, typecheck), fix failures, update the changelog, commit, push, and create/update the pull request or merge request.
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
parallel-pr-review
Use when asked to "review the open PRs", review a batch or stack of pull requests, or run a recurring PR-review pass on a repo — especially with many PRs, stacked branches, conflicts, or security-sensitive changes. Covers grouping, fan-out to review subagents, verdict synthesis, and posting.
release
Cut a Memoria release. Version bump, CHANGELOG, CI workflows, Docker image. Use when publishing a new version.