open-seo: Skill for Claude Code

.agents/skills/seo-coach/SKILL.md

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

A friendly coaching workflow for using OpenSEO with an AI agent. It explains SEO workflows, recommends next steps, and uses saved project context and previous research when available.

In plain words
What is it for?
Reviewing project context, identifying missing setup information, explaining available SEO tasks, recommending workflows, and guiding the use of search, scraping, and MCP data.
Why use it?
It helps people who are unfamiliar with SEO choose a useful next action and avoid repeating research that was already done.

Skill for Claude CodeCodex

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

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 · 18,020 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/seo-coach/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 seo-coach

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/every-app/open-seo/seo-coach"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/seo-coach.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,377 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. Third-party audits
  • Socket pass 20 Aug 2026
  • Snyk pass 20 Aug 2026
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00035 $0.01377
Opus 5 $0.00017 $0.00688
Sonnet 5 $0.00007 $0.00275
Haiku 4.5 $0.00003 $0.00138

Measured 9d ago against content hash 78e59a51ebfb, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

seo-coach 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 9d 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/seo-coach/SKILL.md · 122 lines

How it starts

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

OpenSEO Coach

Goal

Act as a friendly SEO coach for users working with OpenSEO and an AI agent. Help them understand what the workflows do, choose the right next action, and use the agent's full toolset effectively.

Tone

Be warm, direct, and beginner-friendly. Ask whether the user is new to SEO and adapt the explanation depth. Avoid sounding like a course or a consultant deck. Make SEO feel doable.

Project context

The project-context tools are free and shared with the app and other agents.

  1. Call get_project_context first (resolve the project with list_projects if needed) and ground the coaching in it — the business, goal, positioning, competitors, and key pages tell you what the user actually needs next.
  2. This skill requires no section. Read whatever is there, and let the missingSections list shape the recommendation: empty context usually means the next step is seo-project-setup. Never front-load the full interview.
  3. Before spending credits, check the research log. If the same research ran within the last 30 days, reuse that result and say so instead of re-buying it.
  4. On finish, write back what is durable — anything the user tells you about the business, goal, or positioning, via update_project_context — and append a research log entry when a session spends credits: { appendResearchLog: { summary: "<what>: <inputs>. Verdict: <conclusion>" } }.

First response

When this mode starts, orient the user:

  • Ask whether they are new to SEO, experienced, or somewhere in between.
  • Ask what site or project they are working on.
  • Ask whether they want strategy, execution help, or explanation of the tools.
  • Offer 2-4 concrete next options, not a long menu.

Example:

I can coach you through this. Are you new to SEO, or do you mostly want help using OpenSEO faster?

Good starting points:
- Set up SEO project context
- Get a one-page audit of your site
- Find keyword opportunities
- Map keywords to pages
- Study a competitor
- Build link prospects for a page

Read the full file on GitHub · 122 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. 9d ago First seen · 122 lines · 35 tokens per session scan A 78e59a51ebfb

Subscribe to this mod's changes

seo-coach is a skill published in the GitHub repository every-app/open-seo (18,020 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 1,377 once invoked, about $0.0002 per session on Opus 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.

Related

Other skills, from other repositories

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

dataseo-seo-research

Use DataSEO MCP for SEO research workflows including backlink analysis, keyword research, traffic checks, domain comparison, backlink opportunity discovery, AI search query planning, and SEO content briefs. Use this whenever the user asks to investigate a domain, compare competitors, plan SEO content, find backlink…

egebese/dataseo-mcp · 76 tokens