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 SII-Holos/synergy --skill release-log-workflowgit clone --depth 1 https://github.com/SII-Holos/synergyWrote 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/sii-holos/synergy/release-log-workflow)<a href="https://agentmods.dev/skills/sii-holos/synergy/release-log-workflow"><img src="https://agentmods.dev/badge/skills/sii-holos/synergy/release-log-workflow.svg" alt="Measured on agentmods" 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.00068 | $0.00617 |
| Opus 5 | $0.00034 | $0.00309 |
| Sonnet 5 | $0.00014 | $0.00123 |
| Haiku 4.5 | $0.00007 | $0.00062 |
Grade A, and why
release-log-workflow 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 — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Produce a Release Log
Set the Scope
- Confirm the release version, previous comparison point, repository range, date, language, target surfaces, and whether publication is requested.
- Read
references/release-checklist.md. Before any Feishu write, also readreferences/feishu-template.mdfor the current node, title, and index contract. - Do not publish, edit the index, create a GitHub release, or send an announcement when the user asked only for analysis or a draft.
Establish the Shipped Delta
git tag --list --sort=-version:refname | head -20
git log --oneline --decorate <previous>..<release>
git diff --stat <previous>..<release>
Inspect ambiguous commits with git show, targeted diffs, tests, and current product docs. Group the final shipped behavior by product area. Exclude formatting, release mechanics, tests, docs, and implementation churn unless they explain a user-visible capability, compatibility change, or reliability fix.
Draft Once
Create one evidence-backed source note with:
- title and short summary
- at-a-glance changes
- details grouped by product theme
- upgrade or migration notes
- fixes and polish
- restrained next steps when appropriate
Describe final behavior rather than commit chronology. Verify product names against Product overview and current terminology against Documentation.
Derive shorter Wiki-announcement or GitHub Release versions from the same findings; do not re-analyze the range separately.
Publish to Feishu When Authorized
- Fetch the current index before writing and preserve every prior entry.
- Create a dedicated child document under the configured update-log wiki node using the title format in
feishu-template.md. - Fetch the child document and verify its title, sections, links, and content.
- Insert one date/version/link/summary entry at the top of the full index document.
- Overwrite the index only with the complete newest-first content.
- Fetch the index again and verify the new entry, prior entries, order, and child link.
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.
- 8d ago First seen · 53 lines · 68 tokens per session scan A 800b07e46ccc
release-log-workflow is a skill published in the GitHub repository SII-Holos/synergy (548 stars, last pushed yesterday), licensed MIT. It adds 68 tokens to every session and 617 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-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.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
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".
updater_guide
Guidance for checking for and installing Row-Bot updates.