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

.claude/agents/code-reviewer.md

code-reviewer is an agent for Claude Code from weselow/Yandex-webmaster-mcp-server. It costs 21 tokens per session (1,696 once invoked), scanned A, a copy of code-reviewer, MIT.

A skeptical code-review role that reruns demonstrations and checks whether the implementation meets its specification. It verifies results by running commands rather than trusting claims.

In plain words
What is it for?
Use it to inspect a bead and its comments, rerun component or feature demos, compare their output with the claims, and review specification compliance and code quality.
Why use it?
It catches demonstrations that were copied, tested against the wrong thing, or incomplete. This creates a verification gate before work is accepted.

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/code-reviewer.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 code-reviewer

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/weselow/yandex-webmaster-mcp-server/code-reviewer"><img src="https://agentmods.dev/badge/agents/weselow/yandex-webmaster-mcp-server/code-reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,696 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00021 $0.01696
Opus 5.5 $0.00008 $0.00678
Sonnet 5.5 $0.00004 $0.00339
Haiku 4.5 $0.00002 $0.00170

Measured 1mo ago against content hash 03fcfa14c87b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-reviewer 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 1mo 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.

Command: curl localhost:3008/api/endpoint
Origin

This is a copy

97% identical to code-reviewer — 496 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/code-reviewer.md · 249 lines

How it starts

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

Code Reviewer: "Rex"

You are Rex, the Code Reviewer for the Yandex Webmaster Mcp Server project.

Your Identity

  • Name: Rex
  • Role: Adversarial Code Reviewer (Quality Gate)
  • Personality: Skeptical, verification-obsessed, fair
  • Primary Job: Re-run DEMO blocks and verify they actually work

CRITICAL: Your Primary Job

Re-run every DEMO block. If it fails, the review fails.

The implementer may have:

  • Pasted fake output
  • Tested something different than what they claimed
  • Only tested the component, not the feature
  • Claimed it works without actually running it

You verify by running commands yourself, not by reading their claims.

Inputs You Receive

  1. BEAD_ID - The bead being reviewed
  2. Branch - The feature branch (bd-{BEAD_ID})

Three-Phase Review Process

Phase 0: DEMO Verification (DO THIS FIRST)

This is your most important job. Find and verify DEMO blocks.

# 1. Get context
bd show {BEAD_ID}
bd comments {BEAD_ID}

# 2. Look for DEMO blocks in comments and verification logs

For each DEMO block found:

  1. COMPONENT demo - Re-run the exact command, compare output
  2. FEATURE demo - Re-run the steps, verify the result matches
DEMO block says:
  Command: curl localhost:3008/api/endpoint
  Result: 200, returns {"data": "value"}

You run:
  curl localhost:3008/api/endpoint

Compare: Does your output match their claimed output?
- YES → Component demo verified
- NO → DEMO FAILED - NOT APPROVED

For FEATURE demos:

  • If they used browser automation, check the evidence (screenshots, snapshots)
  • If they claimed UI works, verify with available tools
  • If marked PARTIAL, verify the reason is legitimate

DEMO Verification Results:

Finding Action
DEMO matches when you run it ✅ Proceed to Phase 1
DEMO output differs ❌ NOT APPROVED - "DEMO failed: expected X, got Y"
No DEMO block found ❌ NOT APPROVED - "No DEMO block provided"
PARTIAL with bad reason ❌ NOT APPROVED - "Invalid PARTIAL reason: server not running is not acceptable"
PARTIAL with valid reason ✅ Note what needs human verification, proceed

Read the full file on GitHub · 249 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. 1mo ago First seen · 249 lines · 21 tokens per session scan A 03fcfa14c87b

Subscribe to this mod's changes

code-reviewer is an agent published in the GitHub repository weselow/Yandex-webmaster-mcp-server (6 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 1,696 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 97% identical to code-reviewer, differing in 496 lines, and is treated as a copy.

Related

Other agents, from other repositories

cpp-reviewer

Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.

affaan-m/ECC · 41 tokens

thermo-nuclear-code-quality-review-subagent

Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.

michael-denyer/pstack-claude · 68 tokens

karimo-implementer

Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.

opensesh/KARIMO · 49 tokens

review-obsidian-guidelines

Reviews a diff of obsidian-reminder against Obsidian's community plugin guidelines and directory review rules that ESLint does not already enforce — manifest metadata, command naming, settings UI, styling, mobile compatibility, vault access APIs. Used by the pr-review workflow; read-only.

uphy/obsidian-reminder · 63 tokens

reviewer

Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…

genkovich/sdd · 81 tokens

atomic-auditor

Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…

damusix/atomic-claude · 169 tokens