Borrowing it
Nothing to install: this file belongs to md-riaz/google-seo-mcp. 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/md-riaz/google-seo-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/md-riaz/google-seo-mcpWrote 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/md-riaz/google-seo-mcp/agents-md)<a href="https://agentmods.dev/instructions/md-riaz/google-seo-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/md-riaz/google-seo-mcp/agents-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.00671 | $0.00671 |
| Opus 5 | $0.00336 | $0.00336 |
| Sonnet 5 | $0.00134 | $0.00134 |
| Haiku 4.5 | $0.00067 | $0.00067 |
Grade A, and why
google-seo-mcp AGENTS.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 — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Google SEO MCP Server Conventions (AGENTS.md)
This repository contains the Google SEO MCP Server. While this repository itself is a single Node.js project, it is architected and configured to be co-hosted on a shared VPS (Virtual Private Server) alongside other internal MCP servers.
🏛️ Co-Hosting Architecture
graph TD
Client[Claude Code / MCP Client] -->|HTTPS| Nginx[Nginx Reverse Proxy]
Nginx -->|/search-console/*| Port3000[This Google SEO MCP - Port 3000]
Nginx -->|/other-mcp/*| Port3001[Other MCP Server - Port 3001]
-
Co-existence on a VPS:
- Each MCP server hosted on the VPS runs as an independent Node.js service listening on a unique local port (e.g., this server runs on port
3000).
- Each MCP server hosted on the VPS runs as an independent Node.js service listening on a unique local port (e.g., this server runs on port
-
Unified Nginx Reverse Proxy:
- A single Nginx server block handles TLS (SSL) termination and routes traffic to individual MCP servers using subpath routing (e.g.,
/search-consolevs/github). - This server supports the
BASE_PATHenvironment variable so that it listens and exposes endpoints (like/sseand/messages) matching its allocated Nginx subpath. - Why BASE_PATH is necessary inside the project (not just rewritten by Nginx): The SSE Server Transport protocol sends the POST endpoint path (e.g.
/messages) back to the client. If Nginx rewrites the prefix before it reaches Express, the server will tell the client to POST messages to/messagesinstead of/search-console/messages, causing path collisions at the Nginx level. KeepingBASE_PATHinside the application ensures the correct routing path is sent back to the client.
- A single Nginx server block handles TLS (SSL) termination and routes traffic to individual MCP servers using subpath routing (e.g.,
🛠️ Port & Path Allocations (VPS Example)
When hosting other internal MCP servers on the same VPS, ensure you coordinate ports and subpaths to prevent collisions:
| MCP Server Name | Subpath Prefix | Port | Service Location on VPS |
|---|---|---|---|
| Google SEO MCP (This Service) | /search-console |
3000 |
/var/www/google-seo-mcp |
| GitHub MCP (Example) | /github |
3001 |
/var/www/github-mcp |
| Database MCP (Example) | /database |
3002 |
/var/www/database-mcp |
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 · 43 lines · 671 tokens per session scan A 1dee1979e705
google-seo-mcp AGENTS.md is an instructions file published in the GitHub repository md-riaz/google-seo-mcp (1 stars, last pushed 2mo ago), licensed MIT. It adds 671 tokens to every session, about $0.0034 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.