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 agentmods add skills/yoshiko-pg/difit/releasenpx skills add yoshiko-pg/difit --skill releasegit clone --depth 1 https://github.com/yoshiko-pg/difitWrote 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/yoshiko-pg/difit/release)<a href="https://agentmods.dev/skills/yoshiko-pg/difit/release"><img src="https://agentmods.dev/badge/skills/yoshiko-pg/difit/release.svg" alt="Measured on agentmods" 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 | $0.00061 | $0.00647 |
| Opus 5 | $0.00030 | $0.00324 |
| Sonnet 5 | $0.00012 | $0.00129 |
| Haiku 4.5 | $0.00006 | $0.00065 |
Grade A, and why
release 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 4d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Workflow
Follow this workflow for the current repository.
Prepare changelog draft
- Run
./scripts/get-changes-since-tag.sh. - Categorize changes into these sections as needed:
Added,Changed,Deprecated,Removed,Fixed,Security,Thanks. - Use script output rules:
- Use GitHub username from script output.
- Exclude
yoshiko-pgandrenovate[bot]fromThanks. - Include PR numbers when available.
- Order bullets with PR numbers by ascending PR number within each section, and list multiple PR numbers within a bullet in ascending order.
- Use commit subject and body for categorization.
- Consolidate routine dependency-only updates, including grouped dependency updates, package manager bumps, and ordinary individual dependency bumps, into a single
Changedbullet formatted as- Update dependencies (#123 #124 #125); keep a separate bullet only when the dependency change is clearly user-facing beyond routine maintenance.
- Write the categorized content into
CHANGELOG.mdunder## [Unreleased]. - Ask for user confirmation in Japanese.
Release after explicit OK
- The only allowed
CHANGELOG.mdedits after OK are:- insert the new version heading with today's date directly below
## [Unreleased] - place the captured
Unreleasedbody under that new heading unchanged - leave
## [Unreleased]empty - update the bottom compare links for
Unreleasedand the new version
- insert the new version heading with today's date directly below
- Run
npm version --no-git-tag-version patch. - Move current
Unreleasedcontent into a new version section with today's date. - Update bottom links:
- Update
Unreleasedcompare link to new version tag. - Add compare link for the new version.
- Update
- Commit
CHANGELOG.mdandpackage.jsonwith an English message:chore: release vX.Y.Z. - Create tag
vX.Y.Z. - Push
mainand tags:git push origin main --tags. - If push is rejected by non-fast-forward:
- Run
git pull --rebase origin main. - Retry
git push origin main --tags.
- Run
- Build release notes from the new version section text in
CHANGELOG.md. - Create GitHub release on origin:
gh release create vX.Y.Z --title "vX.Y.Z" --notes-file <notes-file>
What ships with it
1 file 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.
- 4d ago First seen · 54 lines · 61 tokens per session scan A 18b91d4c01a7
release is a skill published in the GitHub repository yoshiko-pg/difit (3,131 stars, last pushed 6d ago), licensed MIT. It adds 61 tokens to every session and 647 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-30.
Other skills, from other repositories
release
Cut a Symphony release by bumping the committed version, landing it, tagging the merged commit, and verifying the Burrito release workflow. Use when asked to release, tag, or retag Symphony.
changelog-entry
Add a new entry to CHANGELOG.yml under the current unreleased version (or create the version block if needed), then regenerate documentation. Use when the user says things like "add a changelog entry", "log this fix in the changelog", or "/changelog-entry".
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
mate-oss-gate
在准备把 MateCloud（或其子集）开源 / 发布到公开仓前使用。按 open-core 边界把关：剥离企业代码、清竞品名与内部路径、查密钥、确认 LICENSE。当用户说"要开源了""发布公开版""开源前检查""oss release"时触发。.
devops/changelog-generation
自动生成 CHANGELOG，基于 git 提交历史和 pipeline 产物信息，遵循 Conventional Commits 和 Keep a Changelog 规范.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".