Borrowing it
Nothing to install: this file belongs to upgrade-ventures/upgradeseo. 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/upgrade-ventures/upgradeseo/main/.agents/skills/upgradeseo-release-notes/SKILL.mdgit clone --depth 1 https://github.com/upgrade-ventures/upgradeseoWrote 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/upgrade-ventures/upgradeseo/upgradeseo-release-notes)<a href="https://agentmods.dev/skills/upgrade-ventures/upgradeseo/upgradeseo-release-notes"><img src="https://agentmods.dev/badge/skills/upgrade-ventures/upgradeseo/upgradeseo-release-notes/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/upgrade-ventures/upgradeseo/upgradeseo-release-notes"><img src="https://agentmods.dev/badge/skills/upgrade-ventures/upgradeseo/upgradeseo-release-notes.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.00072 | $0.01771 |
| Opus 5.5 | $0.00029 | $0.00708 |
| Sonnet 5.5 | $0.00014 | $0.00354 |
| Haiku 4.5 | $0.00007 | $0.00177 |
Grade A, and why
upgradeseo-release-notes 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 1mo 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.
This is a copy
91% identical to openseo-release-notes — 24 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UpgradeSEO release notes
Cut a release for this repo end to end. The deliverables are a version bump in package.json, a new release-notes/v<version>.md, and a PR against origin/main titled release: v<version>.
1. Bump the version
- Read
package.json. If the branch has already bumpedversion, treat that as the source of truth and do not change it. - Otherwise bump the patch version (e.g.
0.0.19→0.0.20). Only bump minor/major if explicitly asked.
2. Collect the changes since the last release
- Find the latest tag:
git tag --sort=-creatordate | head -1. Verify the branch is up to date withorigin/main(git fetch origin main && git log HEAD..origin/main --onelineshould be empty; flag it if not). - List commits:
git log <last-tag>..HEAD --oneline. You can also runpnpm release:notesfor a raw commit inventory — use it only as a checklist of candidate changes, never as the draft's structure (its Improved/Changed/Docs sections must not appear in the notes). - For each commit, fetch the PR body and author (
gh pr view <num> --repo <repo> --json title,body,author) — squash-commit subjects can be stale. The(#NN)in commit subjects can reference either repo: tryupgrade-ventures/upgradeseo(origin) first and fall back toupgrade-ventures/upgradeseo(public) — outside contributors' PRs and their handles live on the public repo. Commits with no(#NN)may still be an outside contribution with a public PR (gh pr list --repo upgrade-ventures/upgradeseo --state merged --author <login>); checkgit log --format=%anfor the author. Verify claims against the final code when a PR body and commit subject disagree (features get reverted before merge). - Record the PR author's GitHub handle alongside each change so the bullet can credit them.
3. Draft the notes
Write release-notes/v<version>.md. release-notes/v0.0.24.md is the canonical style exemplar — match it (v0.0.25 and later follow the same style); v0.0.23 and earlier are the old verbose style, never imitate them. The notes are a scannable digest, not documentation: the whole file fits on one screen (roughly 15 lines including headings), and every line earns its place.
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.
- 1mo ago First seen · 71 lines · 72 tokens per session scan A 521f6556de4f
upgradeseo-release-notes is a skill published in the GitHub repository upgrade-ventures/upgradeseo (3 stars, last pushed 2mo ago), licensed MIT. It adds 72 tokens to every session and 1,771 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 91% identical to openseo-release-notes, differing in 24 lines, and is treated as a copy.
Other skills, from other repositories
release
Cut and maintain Observal release branches, prepare alpha, beta, RC, stable, and patch releases, backport merged main PRs, inspect release status, verify published artifacts, and recover failed release operations. Use for Observal maintainer release tasks and release-process changes, not for installing or upgrading an…
release
Prepare, verify, and publish Sutando engine releases. Use when asked to prepare a release proposal, determine a version bump, audit release documentation, validate release gates, create a release PR, tag a confirmed release, or publish GitHub release notes. Preparation is safe and non-publishing; tagging and…
ship-workflow
Resumable shipping lifecycle: reconciles current Git and GitHub facts from any entry (dirty default or feature branch, local commits, published branch, open PR, existing manual or native stack, merged work), commits dirty work as lossless logical commits, publishes or reuses the PR, requires current CI and review…
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".
repo-sentinel
Full security audit for public repositories across 12 attack surfaces: git history, secrets, CI/CD, containers, dependencies, licenses. Triggers on: "push to GitHub", "make repo public", "open source this", "is this safe to push", "release audit", "secret leaks".
changelog-sync
Reusable-session release-notes runbook for {{targetrepo}}. Finds the range since the last release covered, reads every PR merged in it, groups them by area, writes plain-language notes in the house voice, and opens a PR against {{changelogpath}} only when a new release has actually shipped.