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/seo-audit/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/seo-audit)<a href="https://agentmods.dev/skills/every-app/open-seo/seo-audit"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/seo-audit/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/seo-audit"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/seo-audit.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.00034 | $0.03319 |
| Opus 5.5 | $0.00014 | $0.01328 |
| Sonnet 5.5 | $0.00007 | $0.00664 |
| Haiku 4.5 | $0.00003 | $0.00332 |
Grade A, and why
seo-audit 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- seo-audit — 88% identical, 157 lines differ
How it starts
The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSEO SEO Audit
Goal
Find the work that would most improve a site's useful organic traffic, then explain it so a non-expert can act on it. Research broadly; recommend selectively. The report leads with one to three recommendations that either capture meaningfully more qualified search demand or stop a real loss.
Use this when asked for an SEO audit or review of a domain, especially for a shareable report. For expert-facing analysis of a competitor or market, use competitor-analysis or competitive-landscape instead.
Inputs and project context
- Domain to audit and
projectId(list_projects; if no project matches,create_project). - Call
get_project_contextfirst. This skill needsbusiness_overview. If it is empty, infer what the business does from the site, confirm it with the user in one question, write it back withupdate_project_context, and continue. Suggestseo-project-setupat the end for the rest; never front-load the full interview. - Reuse research-log results under 30 days old for discovery. A ranking claim that drives a recommendation still needs a live check made during this audit.
- On finish, write back what is durable with
update_project_context(a correctedbusiness_overview, the pages the report names viaaddKeyPages) and append{ appendResearchLog: { summary: "Site audit: <domain>. Verdict: <conclusion>" } }.
Deliver through the seo-report skill, saving with skill: "seo-audit". If that skill is unavailable, say so and stop before writing HTML.
OpenSEO MCP tools
whoami: confirm the connection and credits before spending. If OpenSEO is not connected, stop and ask the user to connect it.run_site_audit, thenget_audit_status(wait a minute or two between checks),get_audit_issues,get_audit_pages. Leave Lighthouse off unless the user asked for performance depth. Crawl reads are free.get_backlinks_overviewandget_domain_overview: orientation only. Provider traffic and keyword counts are estimates with no single observation date; they are not measured visits.get_ranked_keywords: which queries send which pages traffic. Start with one domain-level call withresultTypes: ["organic"]; usescope: "exact_url"for the specific pages you compare. A page missing from a limited domain sample is not proof it has no rankings. Ranking rows carry their ownlast_updated_time; keyword metric dates are not ranking dates.get_serp_results: the live check behind every ranking claim in the report. The returnedrankcounts every result block, so count organic (unpaid) listings yourself and report the spot with its page, ten spots per page: "#10 (page 1)", "#11 (page 2)". Request depth 20; a page not seen is "not in the first 20 results". Record the exact query, country, language, date, how many organic listings came back, and the matching URL; those details go in the evidence appendix, not the tables. A failed lookup is unknown, not "not in the first 20 results".get_search_console_performance: when connected, first-party clicks and impressions separate low visibility from low click-through. Missing access is a coverage gap, not a blocker.get_keyword_metricsandresearch_keywords: demand for the queries a candidate page targets. One focused metrics batch usually suffices; one research call with 1–3 seeds when a demand gap could change the decision.- Web reading (fetch, scrape, or search): the site's own pages, sitemap, the leading results for a query, and competitor pages.
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.
- 1mo ago Changed · +56 lines · +3 tokens per session 39e2ae3cc8de
- 1mo ago Changed · +12 lines 976769fe3ac4
- 1mo ago First seen · 73 lines · 31 tokens per session scan A 66c406d371ad
seo-audit is a skill published in the GitHub repository every-app/open-seo (25,345 stars, last pushed yesterday), licensed MIT. It adds 34 tokens to every session and 3,319 once invoked, about $0.0001 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
altorank
Run AltoRank through its hosted MCP server: readiness audits, Search Console, keyword research, and SEO drafts into a review queue.
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.
improve-svelte
Survey a whole SvelteKit codebase as a senior Svelte/SvelteKit engineer, using svelte-vitals' scan as evidence, then produce a prioritized audit and self-contained implementation plans for other agents (or cheaper models) to execute. Read-only on source code — it plans improvements, it does not apply them. Use when…
seo-pipeline-llm
4-stage SEO content pipeline: keyword research → competitor scraping → SEO analysis → content creation. Outputs local files, no CMS integration.
seo-pipeline-bash
One-shot SEO content pipeline: scrape keywords from SERP and produce article markdown files via Browser Use SDK or DuckDuckGo fallback.