Borrowing it
Nothing to install: this file belongs to garfiec/Librechat-Mobile. 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/garfiec/Librechat-Mobile/develop/.claude/skills/release-highlights/SKILL.mdgit clone --depth 1 https://github.com/garfiec/Librechat-MobileWrote 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/garfiec/librechat-mobile/release-highlights)<a href="https://agentmods.dev/skills/garfiec/librechat-mobile/release-highlights"><img src="https://agentmods.dev/badge/skills/garfiec/librechat-mobile/release-highlights.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.00094 | $0.01930 |
| Opus 5 | $0.00047 | $0.00965 |
| Sonnet 5 | $0.00019 | $0.00386 |
| Haiku 4.5 | $0.00009 | $0.00193 |
Grade A, and why
release-highlights 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Highlights
Adds a # Highlights section between the badge row and ## What's Changed on a
published release. Nothing else about the release changes.
The invariant
Everything from ## What's Changed down is generated once, at publish time, and cannot
be rebuilt. It carries the compare link, the New Contributors block, the build provenance
attestation ID, and the CI run URL. Those come from the publish-time workflow run. If they
are overwritten they are gone.
So: never regenerate a release body. Never call gh release edit --notes with prose you
composed. Never let gh release create --generate-notes near an existing release. The only
supported write is scripts/insert_highlights.py, which fetches the live body, splits it at
the marker, and reassembles it with the tail byte-identical — then re-fetches and proves the
tail did not change, printing a restore command if it did.
If the script refuses, that refusal is the feature. Do not work around it by editing the body by hand.
Steps
1. Resolve the target
- No argument → the newest release:
gh release list --repo garfiec/Librechat-Mobile --limit 1 - Explicit tags → exactly those, in the order given.
--backfill→ every release with no Highlights section. Enumerate them and confirm before touching any. There are releases going back tov0.1.1that predate both calver and the Switchboard rename; they are almost never what the user meant.--since <tag>sets a floor. Backfill never runs implicitly.
Refuse a tag that already has a Highlights section. Replacing one is a separate, explicit
request, and only then does --replace get passed.
2. Read the release and every PR in it
gh release view "$TAG" --repo garfiec/Librechat-Mobile --json body -q .body
Extract the PR numbers from the What's Changed list, then read every one of them:
for p in $PRS; do
echo "=== #$p"
gh pr view "$p" --json title,body -q '.title + "\n" + (.body | .[0:800])'
done
What ships with it
1 file 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 · 165 lines · 94 tokens per session scan A a07e4ba5463b
release-highlights is a skill published in the GitHub repository garfiec/Librechat-Mobile (88 stars, last pushed yesterday), licensed MIT. It adds 94 tokens to every session and 1,930 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-30.
Other skills, from other repositories
publish-site
Versioned site deploys to GitHub/Cloudflare/Netlify Pages.
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
github
GitHub via gh CLI: PRs, issues, reviews, repos, auth.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
release-notes-generator
Generate release notes in 3 formats (CHANGELOG.md, PR body, Slack announcement) from git commits. Automatically categorizes changes and converts technical language to user-friendly messaging. Use for releases, changelogs, version notes, what's new summaries, or ship announcements.
release-notes
Generate release notes in multiple formats from git commits.