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 hackerFish/awesome-dsh-skills --skill dsh-changeloggit clone --depth 1 https://github.com/hackerFish/awesome-dsh-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/hackerfish/awesome-dsh-skills/dsh-changelog)<a href="https://agentmods.dev/skills/hackerfish/awesome-dsh-skills/dsh-changelog"><img src="https://agentmods.dev/badge/skills/hackerfish/awesome-dsh-skills/dsh-changelog/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/hackerfish/awesome-dsh-skills/dsh-changelog"><img src="https://agentmods.dev/badge/skills/hackerfish/awesome-dsh-skills/dsh-changelog.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.00030 | $0.00234 |
| Opus 5 | $0.00015 | $0.00117 |
| Sonnet 5 | $0.00006 | $0.00047 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
dsh-changelog 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.
What it actually says
维护 CHANGELOG
格式（Keep a Changelog）
## [未发布] - YYYY-MM-DD
### 新增
### 变更
### 修复
### 移除
### 安全
- 每个版本一段，倒序排列；条目写"对用户的影响"而非内部实现
- 每条尽量关联 PR/issue 编号
- 发布时把"未发布"改成版本号与日期
联动规则
- 版本号遵循语义化版本：破坏性变更升主版本，新功能升次版本，修复升补丁
- CHANGELOG 与 package.json 版本号、git tag 三者一致
- 与文档同步：CHANGELOG 里说的变化，README/文档必须一致
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 · 29 lines · 30 tokens per session scan A 5ff4fe2b1bd2
dsh-changelog is a skill published in the GitHub repository hackerFish/awesome-dsh-skills (5 stars, last pushed 8d ago), licensed MIT. It adds 30 tokens to every session and 234 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
finishing-a-development-branch
A process for finishing a completed development branch. A branch is a separate line of code changes that can later be merged or submitted as a pull request.
commit-message
Guidance for writing Git commit messages using Conventional Commits, a common format such as fix, feat, or docs followed by a short description. It focuses on explaining why a change was made.
release-skill
A release checklist for publishing a new software version. It covers changing the version number, creating a Git tag, and publishing a GitHub Release.
market-release
A release workflow for publishing a new version of a software package. It uses release-please to create a release pull request, then creates a tag, a GitHub release, and an npm publication after the pull request is merged.
code-review-zh
A Git-based code review workflow that compares changes from a chosen commit, branch, tag, or merge point. It checks both whether the code follows the repository's written standards and whether it implements the requested specification.
release-deploy
A release and deployment skill for preparing a software project for GitHub publication and putting it online.