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 makifbaysal/tasktrooper --skill release-notes-writinggit clone --depth 1 https://github.com/makifbaysal/tasktrooperWrote 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/makifbaysal/tasktrooper/release-notes-writing)<a href="https://agentmods.dev/skills/makifbaysal/tasktrooper/release-notes-writing"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/release-notes-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/makifbaysal/tasktrooper/release-notes-writing"><img src="https://agentmods.dev/badge/skills/makifbaysal/tasktrooper/release-notes-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.00043 | $0.00697 |
| Opus 5.5 | $0.00017 | $0.00279 |
| Sonnet 5.5 | $0.00009 | $0.00139 |
| Haiku 4.5 | $0.00004 | $0.00070 |
Grade A, and why
release-notes-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 8d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Notes Writing
Overview
Release notes tell users what changed for THEM, not what the team did. The failure mode is internal jargon and a flat list of task titles that mean nothing to a user. Changelogs are for humans, not machines — don't dump git log or task titles verbatim.
Core principle: User-visible outcomes, grouped by Keep a Changelog's categories, in plain language.
Where the material comes from
list_board_tasksfiltered todone/releasedfor the period asked about.get_task_pull_requeston each one for detail (what actually shipped, not just the title).- TaskTrooper has no epic/parent task — deliver the notes in chat, or as a document (
add_task_document) on whichever task the stakeholder names, never a phantom "release epic". - The system's own batch release cut auto-generates
### Features/### Fixessections fromKEY Title. Writing implementation-task-spec titles as action + user-visible object (not an internal component name) makes that auto-generated text usable on its own — keep that in mind even when you're not the one writing this document.
Structure
- Added — new user-visible capability.
- Changed — behavior changes users must know about (a moved button, a changed default).
- Deprecated — soon-to-be-removed, still working.
- Removed — gone.
- Fixed — defects resolved, described by the symptom the user saw, not the internal cause.
- Security — a vulnerability closed; state impact, not exploit detail.
- Action required — anything in Changed/Removed that is breaking: what the user must do and by when.
Write user-facing language, no internal jargon. Put task keys in parentheses for traceability.
Worked Example
## Release 2026-07-16
### Added
- Export a project's tasks to CSV from the board (LLM-142).
### Fixed
- Deleting a task with subtasks no longer shows an error (LLM-150).
### Changed
- Task titles are now capped at 200 characters (LLM-138).
### Action required
- None this release.
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.
- 8d ago First seen · 67 lines · 43 tokens per session scan A 6e23f7580db4
release-notes-writing is a skill published in the GitHub repository makifbaysal/tasktrooper (113 stars, last pushed yesterday), licensed Apache-2.0. It adds 43 tokens to every session and 697 once invoked, about $0.0002 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-10-05.
Other skills, from other repositories
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.
publish-harness
Publish a generated harness to npm — runs the smoke test, signs the witness manifest, and dispatches npm publish --provenance from your tagged release.
release-prep
Prepare release documentation including CHANGELOG entry, announcement text, and validation. Run before tagging a new release.
massgen-release-documenter
Guide for following MassGen's release documentation workflow. This skill should be used when preparing release documentation, updating changelogs, writing case studies, or maintaining project documentation across releases.
hive-maintainer
Discipline for developing Hive itself — PR sizing, review handling, merge discipline, release workflow, delegation, and cleanup hygiene. Use this skill when working on Hive repo changes that span multiple PRs or review cycles.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.