Borrowing it
Nothing to install: this file belongs to bypixels/SEO-MCP-PRO. 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/bypixels/SEO-MCP-PRO/main/CLAUDE.mdgit clone --depth 1 https://github.com/bypixels/SEO-MCP-PROWrote 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/instructions/bypixels/seo-mcp-pro/claude-md)<a href="https://agentmods.dev/instructions/bypixels/seo-mcp-pro/claude-md"><img src="https://agentmods.dev/badge/instructions/bypixels/seo-mcp-pro/claude-md.svg" alt="Measured on agentmods" height="20"></a>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.01527 | $0.01527 |
| Opus 5 | $0.00763 | $0.00763 |
| Sonnet 5 | $0.00305 | $0.00305 |
| Haiku 4.5 | $0.00153 | $0.00153 |
Grade A, and why
SEO-MCP-PRO CLAUDE.md 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 7d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
Project Overview
website-ops-mcp is an MCP server providing 121 tools across 17 modules for Google marketing, website performance, SEO, security, monitoring, accessibility, and Cloudflare integration. Built with TypeScript (strict mode), runs on Node.js 20+ via stdio transport. Includes an optional HTTP dashboard with credential management UI.
Build & Development Commands
pnpm build # Build ESM bundle with tsup (target: node20) + copy dashboard HTML
pnpm start # Run production server (node dist/index.js)
pnpm dashboard # Run with web dashboard enabled (port 3737)
pnpm dev # Development mode with tsx watch
pnpm test # Run tests with vitest
pnpm test:coverage # Tests with coverage
pnpm lint # ESLint (flat config)
pnpm lint:fix # ESLint with auto-fix
pnpm typecheck # tsc --noEmit
pnpm clean # Remove dist/
Note: Build outputs ESM only (not CJS). The dist/index.js has a shebang for CLI use. Dashboard module is code-split (lazy-loaded only when DASHBOARD_ENABLED=true).
Architecture
Entry flow
src/index.ts → loads dotenv, calls startServer() from src/server.ts, registers signal handlers.
src/server.ts (~445 lines) creates the MCP server with stdio transport, initializes AuthManager, calls registerAllTools(), then sets up MCP request handlers for tools, resources, and prompts.
Tool system
Tools are registered in a global Map<string, ToolDefinition> via src/tools/index.ts. Each module directory (google/, performance/, security/, etc.) exports a register*Tools() function and a tools array.
9 tool module groups registered in registerAllTools(): monitoring, security, seo-technical, utilities, google (GTM/GA4/GSC/Ads/Business Profile/Indexing), performance (PageSpeed/CrUX/CWV/Lighthouse), reports (site-health/seo-audit/executive-summary/dashboard-overview), accessibility, cloudflare.
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.
- 7d ago First seen · 93 lines · 1,527 tokens per session scan A 20cfae2563c9
SEO-MCP-PRO CLAUDE.md is an instructions file published in the GitHub repository bypixels/SEO-MCP-PRO (0 stars, last pushed 6mo ago), licensed MIT. It adds 1,527 tokens to every session, about $0.0076 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-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.