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 dork-labs/dorkos --skill writing-changelogsgit clone --depth 1 https://github.com/dork-labs/dorkosWrote 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/dork-labs/dorkos/writing-changelogs)<a href="https://agentmods.dev/skills/dork-labs/dorkos/writing-changelogs"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/writing-changelogs/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/dork-labs/dorkos/writing-changelogs"><img src="https://agentmods.dev/badge/skills/dork-labs/dorkos/writing-changelogs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.03071 |
| Opus 5.5 | $0.00012 | $0.01228 |
| Sonnet 5.5 | $0.00006 | $0.00614 |
| Haiku 4.5 | $0.00003 | $0.00307 |
Grade A, and why
writing-changelogs 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 20d 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 — 268 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Writing Changelogs
Write changelog entries and release notes that humans actually want to read. This skill activates when writing changelog entries, preparing GitHub releases, or reviewing release notes quality.
Sources: Keep a Changelog, Common Changelog
When to Use
- Writing a changelog fragment for a change
- Preparing GitHub release notes via
/system:release - Reviewing changelog entries before release
- Transforming commit messages into user-friendly descriptions
Where entries live: fragments
Unreleased entries do not go in CHANGELOG.md. Each change adds one fragment file
under changelog/unreleased/ — a coordination-free scheme that keeps parallel worktrees from
colliding on a shared [Unreleased] block (ADR 260707-231641; full guide in
changelog/README.md). The workflow:
- Filename —
<YYMMDD-HHMMSS>-<kebab-slug>.md: a timestamp id from.claude/scripts/id.tsfollowed by a short slug. The post-commit hook names it from your commit subject. - Body — optional
covers:frontmatter (which commits this fragment covers; the post-commit hook fills it in, and the PR check reads it so your prose stays free to be rewritten for a human), then one or more### Categoryheadings (Added, Changed, Deprecated, Removed, Fixed, Security) with bullets written per the principles below. One fragment may carry multiple categories. - Creation — the
post-commithook writes a fragment from each conventional commit; curate it (or hand-author one) before opening a PR. Never editCHANGELOG.md's[Unreleased]section — it no longer holds entries. - Release —
/system:releasecompiles all fragments into the new## [X.Y.Z]section and deletes them. Only the release process writesCHANGELOG.md.
The entry-quality guidance below applies identically to fragment bullets.
Core Principles
Changelog entries are user-facing prose, so the writing-for-humans skill sets the readability bar: 9th-grade level, one idea per sentence, benefit before mechanism, every acronym glossed. Read it first. The rules specific to changelogs:
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.
- 20d ago Changed · +2 lines 24427eccd920
- 1mo ago Changed e977597633f8
- 1mo ago First seen · 266 lines · 31 tokens per session scan A 19ec95c74e18
writing-changelogs is a skill published in the GitHub repository dork-labs/dorkos (12 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 3,071 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-08-31.
Other skills, from other repositories
changelog-generator
Use when producing release notes from Conventional Commits, computing the next semantic version from a commit stream, generating CHANGELOG.md, or automating release notes in CI. Triggers on "generate the changelog", "what version bump do these commits require", "release notes", "CHANGELOG", or "semantic version".
shell-scripting
Use when a ticket adds or changes shell scripts — bash automation, CI steps, install or release scripts, git hooks, Makefile recipes — and they must follow the Google Shell Style Guide, be safe under set -euo pipefail (knowing its caveats), quote every expansion, clean up temp files and locks, stay portable across GNU…
stage-10-pr
You are a delivery agent. Push. Create PR. Write audit trail. Close finding. Your output is a merge-ready pull request with a complete audit trail linking every change back to the original finding, through the PRD, to the verification report. The PR description is machine-generated from stage artifacts — not…
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.
version-bump
Automated semantic versioning and release workflow for Claude Code plugins. Handles version increments across package.json, marketplace.json, plugin.json manifests, build verification, git tagging, GitHub releases, and changelog generation. npm publishing is done by the tag-triggered GitHub Actions workflow through…
agent-release-manager
Agent skill for release-manager - invoke with $agent-release-manager.