open-seo: Skill for Claude Code

.agents/skills/ai-prompt-research/SKILL.md

ai-prompt-research is a skill for Claude Code, Codex from every-app/open-seo. It costs 74 tokens per session (2,173 once invoked), scanned A, original, MIT.

Research into the questions people ask AI assistants about a market, the answers they receive, and the websites those answers cite.

In plain words
What is it for?
Use it to find useful groups of AI prompts, compare brand visibility, and identify the domains that receive citations before choosing prompts to track.
Why use it?
Keyword research measures searches on sites such as Google, while this examines questions asked directly to an AI assistant and reveals where a brand appears or is absent.

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 · 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/ai-prompt-research/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 ai-prompt-research

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/every-app/open-seo/ai-prompt-research"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/ai-prompt-research.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,173 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 7 Oct 2026
  • Snyk warn 7 Oct 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.00074 $0.02173
Opus 5.5 $0.00030 $0.00869
Sonnet 5.5 $0.00015 $0.00435
Haiku 4.5 $0.00007 $0.00217

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

Security

Grade A, and why

ai-prompt-research 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 10d 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/ai-prompt-research/SKILL.md · 96 lines

How it starts

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

AI Prompt Research

Goal

Answer "What are people asking ChatGPT about my market, and who gets cited when they do?" with the questions in DataForSEO's dataset, ChatGPT's answers to them, and the sites the answers rely on. Keyword research finds what people type into Google; this finds what they ask an AI assistant.

The deliverable is a short ranked list of prompt groups worth caring about, with where the brand already appears, where it is missing, and which domains own the citations. Tracking those prompts is a separate decision the user makes in Prompt Tracking.

Project context

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

  1. External MCP clients: resolve the project with list_projects, ask only if the match is ambiguous, then call get_project_context. In SAM, use the current project and context already injected into the conversation; SAM has no get_project_context tool and needs no project selection or connection setup.
  2. This workflow needs a brand, its website and a rough idea of what it sells. Reuse business_overview, audience, competitors and key pages. If business_overview is empty, infer it from the site, confirm it in one question, and save it with update_project_context.
  3. Read get_ai_visibility_tracker to learn the saved topics and prompts. Prompts already tracked are marked tracked in research results; do not present them as new ideas. brandMentioned matches the tracker's own brand, whose name is the project name; if the project is not named as people write the brand, treat brand mentions as unknown and say so.
  4. Check the research log for prompt research under 30 days old on the same keywords. Reuse it instead of paying again unless the user asks for fresh data.
  5. On finish, append one line with update_project_context: { updates: [{ appendResearchLog: { summary: "AI prompt research: <keywords>. Verdict: <conclusion>" } }] }.

OpenSEO MCP tools

  • research_ai_visibility_prompts: questions about one keyword, matched in questions and answers and kept only when they ask the keyword phrase or cite sites that rank on Google for it or belong to the project or its competitors, with near-duplicates merged and the most common first. Each prompt has cited sources (with own marked), ownDomainCited, brandMentioned and tracked. One prompt search and one Google results lookup per keyword, cached for 24 hours. US English only. Requires a paid plan in hosted mode.
  • explore_prompt: optional. Asks ChatGPT one prompt through its API and returns today's answer, citations, a brandMentioned flag for highlightBrand, and fanOutQueries, the web searches the model ran before answering. Charged at actual usage per uncached answer; cached answers are free for seven days. Requires a paid plan in hosted mode.
  • list_saved_keywords and, when connected, a bounded get_search_console_performance read: free sources of head terms the business already cares about.

Read the full file on GitHub · 96 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. 10d ago First seen · 96 lines · 74 tokens per session scan A c674d1d7818e

Subscribe to this mod's changes

ai-prompt-research is a skill published in the GitHub repository every-app/open-seo (23,850 stars, last pushed 3d ago), licensed MIT. It adds 74 tokens to every session and 2,173 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-10-07.

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