Borrowing it
Nothing to install: this file belongs to jafreck/Lore. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jafreck/Lore/main/.github/skills/release-draft/SKILL.mdgit clone --depth 1 https://github.com/jafreck/LoreWrote 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/jafreck/lore/release-draft)<a href="https://agentmods.dev/skills/jafreck/lore/release-draft"><img src="https://agentmods.dev/badge/skills/jafreck/lore/release-draft/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/jafreck/lore/release-draft"><img src="https://agentmods.dev/badge/skills/jafreck/lore/release-draft.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.00051 | $0.01202 |
| Opus 5.5 | $0.00020 | $0.00481 |
| Sonnet 5.5 | $0.00010 | $0.00240 |
| Haiku 4.5 | $0.00005 | $0.00120 |
Grade A, and why
release-draft 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 2mo 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Draft Lore Release
Purpose
Run Lore's release workflow end to end:
- inspect the delta since the latest release
- refresh docs based on that delta
- bump the version in both
package.jsonandpackage-lock.json - open a release PR
- merge the PR
- publish a GitHub release with a clear changelog and matching git tag
- trigger the npm publish workflow in
.github/workflows/publish.yml
Repo-specific facts
- Release tags use the format
vX.Y.Z. - The package version must stay in sync in both
package.jsonandpackage-lock.json. - Publishing is triggered by a published GitHub release, not by a local tag push alone.
.github/workflows/publish.ymlruns onrelease.published, so the GitHub release must be published after the PR is merged.
Instructions
When the user asks to draft, prepare, cut, or publish a release:
-
Find the release baseline
- Read the latest GitHub release and latest tag.
- Compare the current target branch, normally
main, against that release tag. - Build a release delta from commits, merged PRs, changed files, and any docs that are now stale.
-
Decide the target version
- If the user supplied a version, use it.
- If the user did not supply a version, infer the likely next semver bump from the delta and ask for confirmation before changing files.
- Always use
vX.Y.Zfor tags andX.Y.Zinside package files.
-
Refresh documentation from the release delta
- Review the changes since the last release and update any docs that no longer match reality.
- Check at least
README.mdanddocs/architecture.md, plus any other documentation affected by the changed behavior. - Do not treat docs as optional for a release PR.
- The release PR should include doc refreshes when the delta changes behavior, APIs, workflows, architecture, or supported capabilities.
-
Create a release branch
- Create a branch for the release work, for example
release/vX.Y.Z. - Never push the release changes directly to
main.
- Create a branch for the release work, for example
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.
- 2mo ago First seen · 120 lines · 51 tokens per session scan A 9462b477d759
release-draft is a skill published in the GitHub repository jafreck/Lore (7 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 1,202 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-08-31.
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.
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.
release
Fully automate a release with version-bump and childhood.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
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.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.