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-report/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-report)<a href="https://agentmods.dev/skills/every-app/open-seo/seo-report"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/seo-report/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-report"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/seo-report.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- Socket pass
- Snyk 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.00047 | $0.05687 |
| Opus 5.5 | $0.00019 | $0.02275 |
| Sonnet 5.5 | $0.00009 | $0.01137 |
| Haiku 4.5 | $0.00005 | $0.00569 |
Grade A, and why
seo-report 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 16d 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 — 265 lines — stays where its author put it; the contents beside it link to each section on GitHub.
OpenSEO Report
Goal
Turn finished research into one self-contained HTML page, saved to the project with save_report, so anyone on the team can open it in the app, read it on a phone, and print it to PDF.
Every OpenSEO skill that produces a recommendation delivers through this skill. Chat gets the link, the verdict, and the leading recommendation with its expected benefit, if there is one. The report gets everything else.
Before you write
- Call
list_reportsfor the project. If a report already covers the same subject for the same period, you are correcting your own run: pass itsreportIdtosave_reportand replace it. A new month, a new competitor, or a different skill is a new report. Never save a near-duplicate. - Titles are unique within a project. Saving a second report under an existing title with no
reportIdis rejected, so either pass thereportIdof the report you are replacing or change the title to name the new subject or period. - To revise an existing report, work from its summary.
get_reportreturns the HTML only withincludeHtml: true, and an 80 KB report is roughly 20,000 tokens, which most clients truncate. Fetch the HTML only when you need to edit a specific passage, and if what comes back looks cut off, send the user to the app instead of saving over it.
Following a template
A project can carry report templates: named, reusable briefs saying who a report is for, which sections it has in what order, how it should sound, and how to sign off. They are listed in project context, and list_report_templates returns the full instructions for each one. Templates belong to a project. To reuse one in another project, list it there and save a copy here.
Use a template only when the user names it, or asks for the kind of report a template's name or description names. A plain skill run ("audit this site") uses the skill's default format. If two match, ask in one line. A template's sections, audience and tone replace the skill's Output format list; the HTML constraints and writing rules never change. Project writing_preferences always apply; a template's tone wins only where they conflict. Pass its templateId to save_report.
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.
- 16d ago Changed · +10 lines 9f147c1c0d08
- 27d ago Changed · +5 lines 51d9558d248e
- 29d ago First seen · 250 lines · 47 tokens per session scan A 487c10fbea1f
seo-report is a skill published in the GitHub repository every-app/open-seo (23,850 stars, last pushed 3d ago), licensed MIT. It adds 47 tokens to every session and 5,687 once invoked, about $0.0002 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-09-18.
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.