open-seo: Skill for Claude Code

.agents/skills/verify-local-mcp/SKILL.md

verify-local-mcp is a skill for Claude Code, Codex from every-app/open-seo. It costs 89 tokens per session (1,285 once invoked), scanned A, original, MIT.

A testing workflow for checking an OpenSEO MCP server from both the network protocol and an AI agent's point of view. MCP is a standard way for an AI agent to call tools provided by another server.

In plain words
What is it for?
Starting a local server, sending protocol-level requests, checking real DataForSEO interactions, and probing whether an agent can use the tools correctly.
Why use it?
It catches both technical communication errors and usability problems such as unclear tool descriptions, oversized results, bad input handling, or broken background tasks.

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 · 25,345 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/verify-local-mcp/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 verify-local-mcp

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/every-app/open-seo/verify-local-mcp"><img src="https://agentmods.dev/badge/skills/every-app/open-seo/verify-local-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 89 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,285 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to high

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • high Excessive Agency · line 48
    Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.
    Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
  • medium Data Exfiltration · line 23
    Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.
    Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00089 $0.01285
Opus 5.5 $0.00036 $0.00514
Sonnet 5.5 $0.00018 $0.00257
Haiku 4.5 $0.00009 $0.00128

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

Security

Grade A, and why

verify-local-mcp scanned grade A with 1 finding 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.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -sS http://<url>/mcp \
.agents/skills/verify-local-mcp/SKILL.md · 72 lines

How it starts

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

Verify local MCP

Two layers, in order. The protocol layer proves the server and provider behave; the consumer layer proves an agent that has never seen the code can use the tools well. They catch different bugs — protocol testing found DataForSEO quirks (zoom-dependent empty SERPs), the consumer probe found ergonomics failures (9KB provider rows overflowing client token budgets, fractional inputs rejected upstream with raw provider errors). Do both.

1. Boot

  • .env.local needs AUTH_MODE=local_noauth and DATAFORSEO_API_KEY (base64 of login:password). Never print the key.
  • Start pnpm dev:agents in the background. The server URL is branch-prefixed: http://<branch-suffix>.open-seo.localhost:1355 (the exact URL is printed on boot; logs tee to .logs/dev-server.log).
  • With local_noauth, /mcp needs no token. Vite hot-reloads server code, so fix → re-call without restarting.
  • After changing a tool's input or output schema, refresh the client's tool discovery (tools/list) or reconnect the MCP client before calling it again. Clients can cache validators from the previous tool list and reject valid results after the provider call has already incurred a charge.

2. Protocol smoke (cheap, deterministic)

Raw JSON-RPC against /mcp — the layer for asserting exact shapes and driving edge cases (resume taskIds, empty results, invalid inputs):

curl -sS http://<url>/mcp \
  -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
# tools/call: {"method":"tools/call","params":{"name":"<tool>","arguments":{...}}}
  • Bootstrap: list_projects, then create_project if empty — most tools need a projectId.
  • Test the happy path AND at least one edge per changed tool: an empty result (obscure query), an invalid identifier, and for queued tools the full lifecycle including resuming with the returned taskId.
  • These are real, billed DataForSEO calls (metering itself short-circuits in local_noauth — billing needs unit tests, not this). Keep depths 10–20.

Read the full file on GitHub · 72 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. 1mo ago Changed · +1 lines 2b16bda20b01
  2. 1mo ago First seen · 71 lines · 89 tokens per session scan A d979799d569a

Subscribe to this mod's changes

verify-local-mcp is a skill published in the GitHub repository every-app/open-seo (25,345 stars, last pushed yesterday), licensed MIT. It adds 89 tokens to every session and 1,285 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). 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

playground

Launches a local WordPress Playground site with The SEO Framework mounted, captures front-end SEO artifacts, and compares before/after plugin states. Use when testing regressions, reproducing bugs, changing meta/sitemap/robots/ schema/oEmbed/admin SEO output, checking WordPress version behavior, plugin conflicts, or…

sybrew/the-seo-framework · 73 tokens

wp-finalize-run

The check detail of the /wp-finalize run, split out of commands/wp-finalize.md so the command stays a short map — bilingual coverage, theme structure, the WP-CLI runtime validation, the GEO and agent-readiness report, and the three demo-parity layers (static, WP-CLI, measured visual parity). Use when /wp-finalize…

yojahny55/claude-wp-builder · 131 tokens

wp-demo-verify-run

The step detail of the /wp-demo-verify run, split out of commands/wp-demo-verify.md so the command stays a short map — Step 2a (the impeccable detector and its gate), Step 2b (the scroll walk, Firefox pass, --no-motion, fractional widths and the exit-code 2 fallback) and Step 3 (reading every finding kind). Use when…

yojahny55/claude-wp-builder · 147 tokens

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

dogfood

Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.

callstack/agent-device · 55 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens