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 jqaisystems/jqai-ai-skills --skill release-announcement-writergit clone --depth 1 https://github.com/jqaisystems/jqai-ai-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/jqaisystems/jqai-ai-skills/release-announcement-writer)<a href="https://agentmods.dev/skills/jqaisystems/jqai-ai-skills/release-announcement-writer"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/release-announcement-writer/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/jqaisystems/jqai-ai-skills/release-announcement-writer"><img src="https://agentmods.dev/badge/skills/jqaisystems/jqai-ai-skills/release-announcement-writer.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.00091 | $0.00701 |
| Opus 5 | $0.00046 | $0.00351 |
| Sonnet 5 | $0.00018 | $0.00140 |
| Haiku 4.5 | $0.00009 | $0.00070 |
Grade A, and why
release-announcement-writer 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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Announcement Writer
Overview
Use this skill to turn a shipped change into clear public release communication. The output should be accurate, concrete, and safe to publish: what changed, why it matters, who it helps, where to try it, and what to do next.
Workflow
- Gather source material: changelog, release tag, README diff, commit list, issue list, screenshots, demo links, website URLs, and target audience.
- Separate facts from interpretation. Facts include version, date, links, changed files, features, fixes, and install steps. Interpretation includes value proposition, positioning, and social copy.
- Identify the release tier:
patch: fixes, docs, copy, small polish.minor: new skill, new workflow, new install path, meaningful usability improvement.major: compatibility change, large repositioning, or breaking behavior.
- Draft the core release summary in plain language before writing channel-specific variants.
- Write only claims supported by the source material. Avoid inflated wording such as "revolutionary", "first", "complete", or "production-grade" unless the source proves it.
- Add links to the most useful destination: release tag, GitHub repo, website case study, docs, or demo asset.
- Finish with a short verification checklist: links work, version is correct, screenshots/GIFs are public-safe, and private implementation details are absent.
Output Set
Create only the formats the user needs. If they ask for a full launch pack, include:
- GitHub release notes: concise title, summary, highlights, install/upgrade notes, links.
- README or website blurb: 1 short paragraph that explains the user-facing value.
- Social post: 1 plain-language announcement with the repo/case-study link.
- Short version: 1-2 sentences for profile READMEs, cards, or newsletters.
- Optional changelog bullets: grouped under Added, Changed, Fixed, Docs, Safety.
Voice
- Be specific and practical.
- Lead with the outcome, not the internal effort.
- Prefer "Added X so users can Y" over "Implemented X".
- Keep technical nouns when they matter to the audience.
- Avoid hype, vague AI claims, and unsupported metrics.
What ships with it
2 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 · 57 lines · 91 tokens per session scan A 913e80539fef
release-announcement-writer is a skill published in the GitHub repository jqaisystems/jqai-ai-skills (3 stars, last pushed 1mo ago), licensed MIT. It adds 91 tokens to every session and 701 once invoked, about $0.0005 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
release-skills
A release workflow for preparing and publishing a new version of a software project. A release is a named version that may include updated version files, release notes, tags, or a GitHub Release.
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
changelog-rules
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.
update-changelog
Update the Unreleased section of CHANGELOG.md based on current changes. No-op if CHANGELOG.md does not exist. Use when the user asks to "update changelog", "add to changelog", "update the changelog", "changelog entry", "add changelog entry", or "log this change".
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
git-workflow
A Git workflow guide for organizing commits, branches, pull requests, releases, and automated version-control tasks. Git is the system developers use to track code changes and collaborate.