Borrowing it
Nothing to install: this file belongs to Klartika/gsc-mcp-server. 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/Klartika/gsc-mcp-server/main/AGENTS.mdgit clone --depth 1 https://github.com/Klartika/gsc-mcp-serverWrote 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/klartika/gsc-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/klartika/gsc-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/klartika/gsc-mcp-server/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.02015 | $0.02015 |
| Opus 5 | $0.01007 | $0.01007 |
| Sonnet 5 | $0.00403 | $0.00403 |
| Haiku 4.5 | $0.00201 | $0.00201 |
Grade A, and why
gsc-mcp-server 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — maintenance guide
Guidance for humans and AI coding agents working on this fork of
AminForou/mcp-gsc. Read this before making changes.
What this fork adds
Upstream is a local (stdio) MCP server for Google Search Console. This fork
adds an optional remote, OAuth 2.1-protected HTTP transport: a self-hostable
server where each user signs in with their own Google account
(webmasters.readonly) — no service accounts, no credential files on disk. It
is built on the MCP Python SDK's OAuth framework (mcp.server.auth), federates
to Google, persists sessions in SQLite, and ships as a container image.
All of this lives in new files under gsc_remote/. The upstream server and
its tools are unchanged.
Hard rules (do not break these)
-
Public repository — no identifiable information. Never commit real domains, emails, hostnames, company names, secrets or tokens. Use only RFC-reserved placeholders (
example.com,<your-host>). Deployment values are supplied only via environment variables set by the deployment. -
Stay rebaseable on upstream. Do not edit
gsc_server.py. Put all fork behaviour ingsc_remote/. The seams into upstream are runtime monkeypatches, not source edits. Periodically:git fetch upstream && git rebase upstream/main.This repository is not a GitHub fork — it shares upstream's history but not its fork network, so there is no "Sync fork" button and
gh repo syncdoes not apply. Theupstreamremote above is the only route, and it works exactly as it would in a fork. A scheduled agent checks this weekly.Documented exceptions, all cheap to re-apply, all for the same reason — upstream ships artefacts describing a local server this fork does not deploy:
README.md: the orientation banner at the top, and the removal of upstream's advertisements for a competing hosted GSC MCP service.- Deleted:
.claude-plugin/,.cursor-plugin/,.mcp.json,mcp.json. They configureuvx mcp-search-console— the local stdio server authenticated by credential files — so installing the plugin would stand up a second GSC server with different auth beside the remote connector this fork exists to provide. They also carry upstream's author and ahomepagepointing at the same hosted service. Without amarketplace.jsonthey were never installable as a plugin anyway. CLAUDE.md: a fork banner pointing here, plus corrections to the three sections that actively misdirect — it told assistants to add tools togsc_server.py(rule 2), gave a test command that skipstests/remote/, and documented only upstream's image. The rest is upstream's and still describes the local server accurately.skills/indexing-audit/SKILL.md: a one-word bug fix, also sent upstream.
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 · 153 lines · 2,015 tokens per session scan A 6719e06a2cc9
gsc-mcp-server AGENTS.md is an instructions file published in the GitHub repository Klartika/gsc-mcp-server (0 stars, last pushed 19d ago), licensed MIT. It adds 2,015 tokens to every session, about $0.0101 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.