OpenSEO is an open-source SEO platform for keyword research, rank tracking, competitor analysis, backlink analysis, site audits, and AI visibility work. It connects SEO data to AI agents through an MCP server and reusable agent skills, while allowing users to supply their own DataForSEO API key and self-host the tool. Catalogue add-ons guide agents through OpenSEO's SEO workflows.
Borrowing it
Nothing to install: this file belongs to every-app/open-seo. 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/every-app/open-seo/main/.agents/skills/openseo-release-notes/SKILL.mdgit clone --depth 1 https://github.com/every-app/open-seoWrote 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/every-app/open-seo/openseo-release-notes)<a href="https://agentmods.dev/skills/every-app/open-seo/openseo-release-notes"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/openseo-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/every-app/open-seo/openseo-release-notes"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/openseo-release-notes.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk warn
- 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.00071 | $0.01791 |
| Opus 5.5 | $0.00028 | $0.00716 |
| Sonnet 5.5 | $0.00014 | $0.00358 |
| Haiku 4.5 | $0.00007 | $0.00179 |
Grade A, and why
openseo-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 27d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- upgradeseo-release-notes — 91% identical, 24 lines differ
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.
OpenSEO release notes
Cut a release for this repo end to end. The deliverables are a version bump in package.json, a new docs/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: trybensenescu/open-seo(origin) first and fall back toevery-app/open-seo(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 every-app/open-seo --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 docs/release-notes/v<version>.md. docs/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.
- 27d ago Changed 5ccac9693aff
- 1mo ago First seen · 71 lines · 71 tokens per session scan A 3402c1f1ebaa
openseo-release-notes is a skill published in the GitHub repository every-app/open-seo (25,345 stars, last pushed yesterday), licensed MIT. It adds 71 tokens to every session and 1,791 once invoked, about $0.0003 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-30.
Other skills, from other repositories
rebranding-strategy
When the user wants to plan or execute a rebrand—domain change, 301 redirects, migration, or announcement. Also use when the user mentions "rebranding," "rebrand," "domain change," "domain migration," "301 redirect," "change domain name," "rebrand announcement," "social media rebrand," "brand launch," or "domain…
pre-release
Runs the pre-release checklist. Sets the readme.txt Stable tag to the version being released, captures every page type (sitemaps, robots, feeds, and the rest of the catalog), and flicks all buttons that the changelog mentions. Use when preparing a release, shipping a WordPress.org update, or when the user asks for the…
goshipit
Pre-launch codebase audit skill. Use this whenever someone is about to ship, deploy, launch, push to main/prod, or merge a release - even without "goshipit" explicitly. Trigger on: "is my app ready?", "can I deploy now?", "pre-deploy check", "review before launch", "is this production-ready?", "check my codebase"…
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
Fully automate a release with version-bump and childhood.
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.