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/jafreck/lore/release-draftnpx skills add jafreck/Lore --skill release-draftgit clone --depth 1 https://github.com/jafreck/LoreWhat 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.00051 | $0.01202 |
| Opus 5 | $0.00026 | $0.00601 |
| Sonnet 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 2d 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.
- 2d 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 16d ago), licensed MIT. It adds 51 tokens to every session and 1,202 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…