Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/appsyogi-com/gsc-mcp-server/copilot-instructionsgit clone --depth 1 https://github.com/AppsYogi-com/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/appsyogi-com/gsc-mcp-server/copilot-instructions)<a href="https://agentmods.dev/instructions/appsyogi-com/gsc-mcp-server/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/appsyogi-com/gsc-mcp-server/copilot-instructions.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.00820 | $0.00820 |
| Opus 5 | $0.00410 | $0.00410 |
| Sonnet 5 | $0.00164 | $0.00164 |
| Haiku 4.5 | $0.00082 | $0.00082 |
Grade A, and why
gsc-mcp-server copilot-instructions.md 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 5d 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.
3. Test MCP tools via HTTP: `gsc-mcp run --http 3333`, then curl `/tools` or POST to `/mcp` How it starts
The opening of the file, as written. The whole thing — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GSC-MCP Copilot Instructions
Project Overview
This is a Model Context Protocol (MCP) server that provides Google Search Console (GSC) API access to AI clients (Claude, Cursor, VS Code Copilot). It's distributed as a CLI tool via npm (gsc-mcp) with OAuth/service account authentication.
Architecture
src/
├── index.ts # Public exports for programmatic use
├── types.ts # Zod schemas & TypeScript types (single source of truth)
├── cli/ # Commander-based CLI (`gsc-mcp init|doctor|run`)
├── server/ # MCP server implementation
│ ├── index.ts # Server factory with stdio/HTTP transports
│ ├── tools/ # MCP tools organized by domain (searchAnalytics, sitemaps, etc.)
│ └── resources/ # MCP resources
├── gsc/client.ts # GSC API wrapper with retry logic & pagination
├── auth/ # OAuth2 + service account auth, token storage (keytar/file)
└── cache/sqlite.ts # SQLite cache with TTL for query results
Key data flows:
- CLI commands →
createServer()→ MCP transport (stdio for clients, HTTP for debugging) - Tool calls →
handleToolCall()routes to domain handlers →GSCClient→ Google API - Tokens stored via
keytar(OS keychain) with file fallback; config inenv-pathsdirectories
Development Commands
npm run build # tsup build (ESM, Node 18+)
npm run dev # Watch mode
npm run typecheck # tsc --noEmit
npm run lint # eslint src/
gsc-mcp run --http 3333 # Debug server with HTTP endpoints
Code Conventions
Adding New MCP Tools
- Create tool definition in
src/server/tools/<domain>.tsfollowing the pattern:- Export
<domain>Toolsarray withname,description,inputSchema - Export
handle<Domain>Tool(name, args)handler function
- Export
- Register in
src/server/tools/index.tsby adding togetAllTools()and routing inhandleToolCall() - Tool names use dot notation:
searchanalytics.query,opportunities.lowCtrHighPos
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.
- 5d ago First seen · 79 lines · 820 tokens per session scan A 500ea7954c7e
gsc-mcp-server copilot-instructions.md is an instructions file published in the GitHub repository AppsYogi-com/gsc-mcp-server (4 stars, last pushed 7mo ago), licensed MIT. It adds 820 tokens to every session, about $0.0041 per session on Opus 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-31.
Other instructions, from other repositories
ddgs AGENTS.md
Instructions for deedy5/ddgs, covering agents.md — guide for coding agents, project overview, build / lint / test commands, setup (creates .venv, installs dev deps) and lint (ruff check + mypy type-check).
memory AGENTS.md
Instructions for sunbeamdotpt/memory, covering sunbeam-memory — agent guide, project overview, runtime modes, semantic memory search (optional) and technology stack.
mcp-deep-search CLAUDE.md
Claude Code instructions for just-every/mcp-deep-search, covering claude.md, project overview, core modules & files, commands and development.
web-forager AGENTS.md
AGENTS.md instructions for CyranoB/web-forager, covering repository guidance, purpose, change contract, development and agent workflow references.
web-forager CLAUDE.md
Claude Code instructions for CyranoB/web-forager, a project described as: A search-and-fetch toolkit for AI agents, available as an MCP server and as standalone Agent Skills.
blockrun-mcp AGENTS.md
AGENTS.md instructions for BlockRunAI/blockrun-mcp, covering blockrun mcp, commands, project structure, key dependencies and install in codex.