open-seo: Skill for Claude Code

.agents/skills/setup-openseo/SKILL.md

setup-openseo is a skill for Claude Code, Codex from every-app/open-seo. It costs 38 tokens per session (1,527 once invoked), scanned A, original, MIT.

A setup guide for connecting OpenSEO, an SEO service for improving how websites are found in search engines, to an AI coding agent. It covers the official plugin and a fallback connection using MCP, a standard way for tools to expose capabilities to an agent.

In plain words
What is it for?
Use it to install or connect OpenSEO, sign in, and configure its plugin, MCP endpoint, or SEO skills for the current agent.
Why use it?
It gives the agent a supported connection path while avoiding duplicate integrations and preserving existing ones.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: mentions Claude Code; installed under .agents/ (shared by several agents); mentions Codex.

This is every-app/open-seo's own configuration. It tells Claude Code and Codex how to work on open-seo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything open-seo configures →

About the project

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.

every-app/open-seo · 23,850 stars · on GitHub · openseo.so

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/every-app/open-seo/main/.agents/skills/setup-openseo/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/every-app/open-seo

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for setup-openseo

README.md
[![agentmods](https://agentmods.dev/badge/skills/every-app/open-seo/setup-openseo/github.svg)](https://agentmods.dev/skills/every-app/open-seo/setup-openseo)
Your own site
<a href="https://agentmods.dev/skills/every-app/open-seo/setup-openseo"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/setup-openseo/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.

agentmods 80×15 button for setup-openseo

Your own site · 80×15
<a href="https://agentmods.dev/skills/every-app/open-seo/setup-openseo"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/setup-openseo.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,527 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00038 $0.01527
Opus 5.5 $0.00015 $0.00611
Sonnet 5.5 $0.00008 $0.00305
Haiku 4.5 $0.00004 $0.00153

Measured 2d ago against content hash 30e56158f7de, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

setup-openseo 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 2d 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.

.agents/skills/setup-openseo/SKILL.md · 85 lines

How it starts

The opening of the file, as written. The whole thing — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Set up OpenSEO in this agent. Do what you can; guide me through anything that needs my input.

1. Check this agent

  • Identify this agent and its version. Ask only if you cannot tell.
  • Check for an existing OpenSEO connection. Preserve other integrations and avoid duplicates.
  • Check for OpenSEO skills separately. A connection without skills is incomplete.

2. If this is ChatGPT

If I pasted this into a regular ChatGPT conversation (web or desktop app, not Codex), you cannot install OpenSEO from here. Don't run commands or edit files. Instead, give me these steps and stop:

  1. On chatgpt.com, open Settings → Security and login and turn on Developer mode. This works on Free and paid plans; no upgrade is needed.
  2. Open Settings → Plugins → Developer mode (or Plugins → + → Create MCP App). Name it OpenSEO, enter the server URL https://app.openseo.so/mcp in full, including https:// (otherwise ChatGPT reports "Unsafe URL"), and keep OAuth selected.
  3. Create it, sign in to OpenSEO, and approve the connection.
  4. Start a new chat, select OpenSEO from the + menu, and send: "Use OpenSEO to check my connection and list my projects."

Link the ChatGPT setup guide for screenshots and troubleshooting. If OpenSEO is self-hosted, ChatGPT needs a publicly reachable HTTPS URL; point me to the self-hosting guide instead. If I'm in Codex, continue below.

3. Install the plugin first

The official plugin bundles MCP + SEO skills, with OpenSEO namespacing and shared updates.

  • Codex: follow the plugin guide.
  • Claude Code: follow the plugin guide.
  • Claude Cowork or the Claude desktop app: you cannot install plugins from this chat, so don't run commands. Tell me to open Customize (in Cowork, the Cowork tab first) → Plugins → + or Add → Add marketplace → Add from a repository, enter https://github.com/every-app/open-seo, and install OpenSEO. Then I start a new task and type / to check that OpenSEO skills appear. If I already have a custom OpenSEO connector, have me remove it once the plugin signs in. Plugins need a paid plan. The plugin connects only to hosted OpenSEO, so skip it if https://app.openseo.so/mcp is not on openseo.so (self-hosted) or I'm on Free. Instead, have me add that endpoint under Customize → Connectors → Add custom connector and upload the public skills in Customize → Skills. Then continue at step 5.
  • Other agents: verify plugin compatibility in their current documentation.
  • Check the installed client's help before running commands.

Read the full file on GitHub · 85 lines

Changes

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.

  1. 2d ago Changed · +16 lines 30e56158f7de
  2. 1mo ago First seen · 69 lines · 38 tokens per session scan A 1957f61c69e7

Subscribe to this mod's changes

setup-openseo is a skill published in the GitHub repository every-app/open-seo (23,850 stars, last pushed 3d ago), licensed MIT. It adds 38 tokens to every session and 1,527 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-13.

Related

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.

sickn33/agentic-awesome-skills · 30 tokens

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…

oekazuma/svelte-vitals · 109 tokens

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.

axelfreeman/yandex-wordstat-guide · 84 tokens

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…

oekazuma/svelte-vitals · 136 tokens

seo-pipeline-llm

4-stage SEO content pipeline: keyword research → competitor scraping → SEO analysis → content creation. Outputs local files, no CMS integration.

attaxr/attaxr-seo-pipeline · 33 tokens

seo-pipeline-bash

One-shot SEO content pipeline: scrape keywords from SERP and produce article markdown files via Browser Use SDK or DuckDuckGo fallback.

attaxr/attaxr-seo-pipeline · 32 tokens