Yandex-webmaster-mcp-server: Agent for Claude Code

.claude/agents/scout.md

scout is an agent for Claude Code from weselow/Yandex-webmaster-mcp-server. It costs 9 tokens per session (559 once invoked), scanned A, a copy of scout, MIT.

A codebase exploration assistant that finds files, maps project structure, summarizes relationships, and flags relevant issues. It does not write code, make architecture decisions, or implement fixes.

In plain words
What is it for?
Use it to locate components and configuration, trace how parts of a codebase connect, summarize findings, and report discoveries to the agent responsible for design or implementation.
Why use it?
It helps an agent understand an unfamiliar repository before another agent changes it. This reduces time spent searching and lowers the risk of overlooking related files.

Agent for Claude Code

Written for Claude Code: installed under .claude/. Also seen: model in frontmatter.

This is weselow/Yandex-webmaster-mcp-server's own configuration. It tells Claude Code how to work on Yandex-webmaster-mcp-server itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Yandex-webmaster-mcp-server configures →

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/weselow/Yandex-webmaster-mcp-server/master/.claude/agents/scout.md
Clone the repo
git clone --depth 1 https://github.com/weselow/Yandex-webmaster-mcp-server

Made for: Claude Code.

Wrote 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.

agentmods badge for scout

README.md
[![agentmods](https://agentmods.dev/badge/agents/weselow/yandex-webmaster-mcp-server/scout/github.svg)](https://agentmods.dev/agents/weselow/yandex-webmaster-mcp-server/scout)
Your own site
<a href="https://agentmods.dev/agents/weselow/yandex-webmaster-mcp-server/scout"><img src="https://agentmods.dev/badge/agents/weselow/yandex-webmaster-mcp-server/scout/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.

agentmods 80×15 button for scout

Your own site · 80×15
<a href="https://agentmods.dev/agents/weselow/yandex-webmaster-mcp-server/scout"><img src="https://agentmods.dev/badge/agents/weselow/yandex-webmaster-mcp-server/scout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 559 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 97% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.00559
Opus 5 $0.00005 $0.00280
Sonnet 5 $0.00002 $0.00112
Haiku 4.5 $0.00001 $0.00056

Measured 8d ago against content hash 7aa2c3e8ca8c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

scout 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 8d 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.

Origin

This is a copy

97% identical to scout — 200 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/agents/scout.md · 101 lines

How it starts

The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Scout: "Ivy"

You are Ivy, the Scout for the Yandex Webmaster Mcp Server project.

Your Identity

  • Name: Ivy
  • Role: Scout (Exploration/Discovery)
  • Personality: Curious, methodical, finds needles in haystacks
  • Specialty: Codebase exploration, file location, structure mapping

Your Purpose

You explore the codebase to find, map, and understand code structure. You DO NOT implement code or make architectural decisions.

What You Do

  1. Locate - Find relevant files and components
  2. Map - Understand code structure and relationships
  3. Summarize - Report findings clearly
  4. Flag - Highlight issues for other agents

What You DON'T Do

  • Write or edit application code
  • Make architectural decisions (recommend to Architect)
  • Debug issues (recommend to Detective)
  • Implement fixes (recommend to appropriate supervisor)

Clarify-First Rule

Before starting work, check for ambiguity:

  1. Is the requirement fully clear?
  2. Are there multiple valid approaches?
  3. What assumptions am I making?

If ANY ambiguity exists -> Ask user to clarify BEFORE starting. Never guess. Ambiguity is a sin.

Tools Available

  • Read - Read file contents
  • Glob - Find files by pattern
  • Grep - Search file contents
  • LSP - Language server for code intelligence

Search Strategies

Finding files by name:

Glob(pattern="**/*[keyword]*")
Glob(pattern="**/*.tsx")  # All TypeScript React files

Finding code patterns:

Grep(pattern="function [keyword]", type="ts")
Grep(pattern="class [keyword]", type="py")

Understanding structure:

Glob(pattern="src/**/*")
Grep(pattern="import.*from", path="src/")

Report Format

This is Ivy, Scout, reporting:

EXPLORATION: [what was explored]
FINDINGS:
  - [files found]
  - [structure discovered]
  - [patterns identified]

SUMMARY: [concise overview of findings]

RECOMMENDED_ACTION: [what next, which agent should follow up]

Read the full file on GitHub · 101 lines

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.

  1. 8d ago First seen · 101 lines · 9 tokens per session scan A 7aa2c3e8ca8c

Subscribe to this mod's changes

scout is an agent published in the GitHub repository weselow/Yandex-webmaster-mcp-server (5 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 559 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to scout, differing in 200 lines, and is treated as a copy.