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/merge-ready/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/merge-ready)<a href="https://agentmods.dev/skills/every-app/open-seo/merge-ready"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/merge-ready/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/merge-ready"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/merge-ready.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk pass
- 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.00084 | $0.00445 |
| Opus 5.5 | $0.00034 | $0.00178 |
| Sonnet 5.5 | $0.00017 | $0.00089 |
| Haiku 4.5 | $0.00008 | $0.00044 |
Grade A, and why
merge-ready 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 13d 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:
- merge-ready — 100% identical, 67 lines differ
What it actually says
Get this branch ready for the maintainer's final review. If you were also asked to build something, build it first.
Fetch and merge origin/main if the branch is behind. Then review everything on the branch against it, including uncommitted and untracked files. Make sure you understand every product decision and change in functionality.
Is it secure?
Is it as simple as it can be? What can be deleted or simplified given the end state of the branch? Did an unlikely edge case lead to overengineering? We prefer to delete code.
Does it use APIs and SDKs (TanStack, DataForSEO, Autumn, Cloudflare) idiomatically? Watch for code that reinvents what they already do, works around limits they don't have, or pays for more than it needs. Check the docs only when something looks off.
Is there a significant way to abuse billing, like getting credits, paid features, or provider calls without paying? Ignore small leaks nobody would bother exploiting.
Beyond that, review it however you think best. Work out which parts could do the most damage if they're wrong and spend your time there. docs/maintainers/review-guidelines.md lists the repo's invariants and the things that look wrong but are intentional.
Fix what's real. Commit as you go. Get pnpm ci:check and pnpm test passing locally, then push. Those local runs stand in for CI, so don't wait for GitHub CI to finish.
Open or update the PR against main. Write the description in the simple-issue-description format, and put anything you left for the maintainer's judgment under Extra context.
Never merge. The maintainer reviews last.
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.
- 13d ago Changed · +84 tokens per session 905830e08a53
- 21d ago Changed · -45 lines · -93 tokens per session c2f08d781a85
- 27d ago Changed 0b3f8b2997b4
- 1mo ago First seen · 72 lines · 93 tokens per session scan A d1749f91b99f
merge-ready is a skill published in the GitHub repository every-app/open-seo (25,345 stars, last pushed yesterday), licensed MIT. It adds 84 tokens to every session and 445 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
svelte-vitals
Use when writing or reviewing SvelteKit routes/components — svelte-vitals rule knowledge (SEO, performance, correctness, security, architecture, accessibility) and how to run the scanner.
altorank
Run AltoRank through its hosted MCP server: readiness audits, Search Console, keyword research, and SEO drafts into a review queue.
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…
design-standards
Apply production-grade design standards when building or reviewing pages, components, or UI. Use this skill whenever the user asks to build a page, design a component, lay out a section, review the UI, fix the layout, or check design quality. Triggers on build a page, create a component, design a section, hero, card…
setup-svelte-vitals
Set up svelte-vitals in a SvelteKit project: inspect what the project already uses, derive a svelte-vitals.config from its markuplint / eslint-plugin-check-file config and its actual directory conventions, measure each candidate rule before adopting it, and hand the remaining targets to svelte-vitals install. Use when…
wordstat-collector
A tool that collects search statistics from Yandex Wordstat, the Yandex service for researching what people search for. It returns search phrases and their frequencies for Russian-language market research.