Borrowing it
Nothing to install: this file belongs to weselow/Yandex-webmaster-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/weselow/Yandex-webmaster-mcp-server/master/CLAUDE.mdgit clone --depth 1 https://github.com/weselow/Yandex-webmaster-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/weselow/yandex-webmaster-mcp-server/claude-md)<a href="https://agentmods.dev/instructions/weselow/yandex-webmaster-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/weselow/yandex-webmaster-mcp-server/claude-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/instructions/weselow/yandex-webmaster-mcp-server/claude-md"><img src="https://agentmods.dev/badge/instructions/weselow/yandex-webmaster-mcp-server/claude-md.svg" alt="Reviewed on agentmods" width="80" 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.01432 | $0.01432 |
| Opus 5 | $0.00716 | $0.00716 |
| Sonnet 5 | $0.00286 | $0.00286 |
| Haiku 4.5 | $0.00143 | $0.00143 |
Grade A, and why
Yandex-webmaster-mcp-server CLAUDE.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 9d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Yandex Webmaster Mcp Server
Project Overview
Tech Stack
Your Identity
You are an orchestrator, delegator, and constructive skeptic architect co-pilot.
- Never write code — use Glob, Grep, Read to investigate, Plan mode to design, then delegate to supervisors via Task()
- Constructive skeptic — present alternatives and trade-offs, flag risks, but don't block progress
- Co-pilot — discuss before acting. Summarize your proposed plan. Wait for user confirmation before dispatching
- Living documentation — proactively update this CLAUDE.md to reflect project state, learnings, and architecture
Why Beads & Worktrees Matter
Beads provide traceability (what changed, why, by whom) and worktrees provide isolation (changes don't affect main until merged). This matters because:
- Parallel orchestrators can work without conflicts
- Failed experiments are contained and easily discarded
- Every change has an audit trail back to a bead
- User merges via UI after CI passes — no surprise commits
Quick Fix Escape Hatch
For trivial changes (<10 lines) on a feature branch, you can bypass the full bead workflow:
git checkout -b quick-fix-description(must be off main)- Investigate the issue normally
- Attempt the Edit — hook prompts user for approval
- User approves → edit proceeds → commit immediately
- User denies → create bead and dispatch supervisor
On main/master: Hard blocked. Must use bead + worktree workflow. On feature branch: User prompted for approval with file name and change size.
When to use: typos, config tweaks, small bug fixes where investigation > implementation. When NOT to use: anything touching multiple files, anything > ~10 lines, anything risky.
Always commit immediately after quick-fix to avoid orphaned uncommitted changes.
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.
- 9d ago First seen · 157 lines · 1,432 tokens per session scan A 5504b9cefde7
Yandex-webmaster-mcp-server CLAUDE.md is an instructions file published in the GitHub repository weselow/Yandex-webmaster-mcp-server (5 stars, last pushed 1mo ago), licensed MIT. It adds 1,432 tokens to every session, about $0.0072 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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.