Borrowing it
Nothing to install: this file belongs to pijusz/mcp-gsc. 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/pijusz/mcp-gsc/master/AGENTS.mdgit clone --depth 1 https://github.com/pijusz/mcp-gscWrote 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/pijusz/mcp-gsc/agents-md)<a href="https://agentmods.dev/instructions/pijusz/mcp-gsc/agents-md"><img src="https://agentmods.dev/badge/instructions/pijusz/mcp-gsc/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.00870 | $0.00870 |
| Opus 5 | $0.00435 | $0.00435 |
| Sonnet 5 | $0.00174 | $0.00174 |
| Haiku 4.5 | $0.00087 | $0.00087 |
Grade A, and why
mcp-gsc 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 6d 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent Guidelines for mcp-gsc
Project Structure
src/
├── index.ts # Entry point (stdio transport + setup dispatch)
├── server.ts # McpServer creation + tool registration
├── auth/
│ ├── index.ts # Auth router + getAuthHeaders() (just Bearer token)
│ ├── oauth.ts # OAuth 2.0 token load/refresh
│ ├── service-account.ts # Service account JWT auth
│ └── setup.ts # Interactive credential + config helper
├── config/
│ └── env.ts # Zod-validated env vars + .env file loading
├── services/
│ ├── gsc-api.ts # Central REST client with retry logic
│ ├── format.ts # Markdown table / CSV formatters
│ ├── rate-limiter.ts # URL Inspection rate tracking (600 QPM + 2K/day)
│ └── property-resolver.ts # Auto-resolve GSC property format
├── tools/
│ ├── index.ts # Barrel: registers all tools on server
│ ├── sites.ts # list_properties, get_property_details
│ ├── analytics.ts # search_analytics (core)
│ ├── sitemaps.ts # list_sitemaps, get_sitemap + write tools
│ ├── inspection.ts # inspect_url, batch_inspect_urls
│ ├── export.ts # export_csv
│ ├── sites-write.ts # add_site, delete_site (gated)
│ ├── reporting.ts # performance_overview, compare_periods, top_movers, device_country_breakdown
│ ├── seo.ts # quick_wins, cannibalization, opportunity_finder, position_tracking, ctr_anomalies, content_decay, weekly_seo_report
│ └── technical.ts # indexing_coverage, sitemap_health
└── utils/
├── logger.ts # stderr-only logger
└── property.ts # URL encoding, domain extraction, brand name extraction
Authentication
Two methods (auto-detected from credentials file):
- OAuth 2.0 — Run
bun run setupto authorize interactively - Service Account — Auto-detected if credentials file has
type: "service_account"
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.
- 6d ago First seen · 75 lines · 870 tokens per session scan A d950591178b1
mcp-gsc AGENTS.md is an instructions file published in the GitHub repository pijusz/mcp-gsc (1 stars, last pushed 1mo ago), licensed MIT. It adds 870 tokens to every session, about $0.0043 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
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.
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).
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).
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.
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.