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/ehukaimedia/google-webmaster-mcp/agents-mdgit clone --depth 1 https://github.com/ehukaimedia/google-webmaster-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/ehukaimedia/google-webmaster-mcp/agents-md)<a href="https://agentmods.dev/instructions/ehukaimedia/google-webmaster-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/ehukaimedia/google-webmaster-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 | $0.00316 | $0.00316 |
| Opus 5 | $0.00158 | $0.00158 |
| Sonnet 5 | $0.00063 | $0.00063 |
| Haiku 4.5 | $0.00032 | $0.00032 |
Grade A, and why
google-webmaster-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 3d 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.
What it actually says
Agent Instructions
Mandatory Spec-Driven Architecture
- Maintainer specs live locally in
docs/specs/. - Maintainer plans live locally in
docs/plans/. - Handoffs live locally in
docs/handoffs/<agent><reference>-<date>.md. - Code reviews and audits live locally in
docs/code-reviews/<agent>-<reference>-<date>.md. - Architecture and spec playgrounds live locally under
docs/playgrounds/. - These maintainer artifacts are intentionally ignored by git for the public repo. Keep public-facing documentation in
README.md,SEO_AUDIT_CLI.md,GWMPC_Workflow.md,CONTRIBUTING.md,SECURITY.md, andCHANGELOG.md.
Required Skills
Use the Ehukai OSS Standard for public-readiness, npm-publish, CI, repo-health, dependency, security, and release work.
Use playground, playground-architect, playground-lifecycle, and removing-regression-context when creating or updating architecture/spec artifacts.
Use the google-webmaster-mcp operating skill for GTM, GSC, GA4, sitemap, and google-webmaster-* CLI workflows.
Release Safety
- Do not make the repository public until credentials are rotated, history is purged, and secret scanning is green.
- Do not publish to npm until
npm run cipasses from a clean tagged commit. - Do not run destructive GTM commands without explicit confirmation.
- Preserve public CLI command names unless a downstream migration is landed first.
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.
- 3d ago First seen · 26 lines · 316 tokens per session scan A bb48643f4487
google-webmaster-mcp AGENTS.md is an instructions file published in the GitHub repository ehukaimedia/google-webmaster-mcp (0 stars, last pushed 14d ago), licensed ISC. It adds 316 tokens to every session, about $0.0016 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
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.