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

.claude/skills/subagents-discipline/SKILL.md

subagents-discipline is a skill for Claude Code from weselow/Yandex-webmaster-mcp-server. It costs 11 tokens per session (997 once invoked), scanned B, original, MIT.

A set of engineering rules for implementation work, meaning changes made to software or its data. It tells an agent to read the task context and inspect real data before writing code.

In plain words
What is it for?
Use it when implementing fixes or features, especially work involving external data. It provides a checklist for reading task comments, investigating inputs, and handling edge cases.
Why use it?
It reduces mistakes caused by missing task history or assumptions about database fields, APIs, files, and configuration. The goal is to base changes on observed facts.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents.

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/skills/subagents-discipline/SKILL.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 subagents-discipline

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/weselow/yandex-webmaster-mcp-server/subagents-discipline"><img src="https://agentmods.dev/badge/skills/weselow/yandex-webmaster-mcp-server/subagents-discipline.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 11 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 997 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found 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.00011 $0.00997
Opus 5 $0.00005 $0.00498
Sonnet 5 $0.00002 $0.00199
Haiku 4.5 $0.00001 $0.00100

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

Security

Grade B, and why

subagents-discipline scanned grade B with 2 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 12d 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.

Sends data to an external URLmediumData exfiltration

A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.

curl -X POST localhost:3000/api/users -d '{"name":"test"}' -H "Content-Type: application/json"

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

| API endpoint | `curl` the endpoint, check response | Write integration test |
.claude/skills/subagents-discipline/SKILL.md · 128 lines

How it starts

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

Implementation Principles

Rule 0: Read the Bead First

Before implementing anything, read the bead comments for context:

bd show {BEAD_ID}
bd comments {BEAD_ID}

The orchestrator's dispatch prompt is automatically logged as a DISPATCH comment on the bead. This contains:

  • The investigation findings
  • Root cause analysis (file, function, line)
  • Related files that may need changes
  • Gotchas and edge cases

Use this context. Don't re-investigate. The comments contain everything you need to implement confidently.

If no dispatch or context comments exist, ask the orchestrator to provide context before proceeding.


Rule 1: Look Before You Code

Before writing code that touches external data (API, database, file, config):

  1. Fetch/read the ACTUAL data - run the command, see the output
  2. Note exact field names, types, formats - not what docs say, what you SEE
  3. Code against what you observed - not what you assumed
WITHOUT looking first:
  Assumed: column is "reference_images"
  Reality: column is "reference_image_url"
  Result:  Query fails

WITH looking first:
  Ran: SELECT column_name FROM information_schema.columns WHERE table_name = 'assets';
  Saw: reference_image_url
  Coded against: reference_image_url
  Result: Works

Rule 2: Test Functionally (Close the Loop)

Principle: Optimize for the fastest way to verify your work actually works.

You built Fast verification Slower alternative
API endpoint curl the endpoint, check response Write integration test
Database change Run migration, query the result Write migration test
Frontend component Load in browser, interact with it Write component test
CLI tool Run the command, check output Write unit test
Config change Restart service, verify behavior N/A — just verify

Two strategies:

  1. User Journey Tests — Test actual behavior as a user experiences it:
    # API: curl with real data
    curl -X POST localhost:3000/api/users -d '{"name":"test"}' -H "Content-Type: application/json"
    
    # CLI: run the command
    bd create "Test" -d "Testing" && bd list
    
    # Error case: curl with invalid auth
    curl -X POST localhost:3000/api/users -H "Authorization: Bearer invalid"
    

Read the full file on GitHub · 128 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. 12d ago First seen · 128 lines · 11 tokens per session scan B facb3eb5c28c

Subscribe to this mod's changes

subagents-discipline is a skill published in the GitHub repository weselow/Yandex-webmaster-mcp-server (5 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 997 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens