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/skills/dev-standards/SKILL.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/skills/weselow/yandex-webmaster-mcp-server/dev-standards)<a href="https://agentmods.dev/skills/weselow/yandex-webmaster-mcp-server/dev-standards"><img src="https://agentmods.dev/badge/skills/weselow/yandex-webmaster-mcp-server/dev-standards/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/skills/weselow/yandex-webmaster-mcp-server/dev-standards"><img src="https://agentmods.dev/badge/skills/weselow/yandex-webmaster-mcp-server/dev-standards.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.00074 | $0.01142 |
| Opus 5.5 | $0.00030 | $0.00457 |
| Sonnet 5.5 | $0.00015 | $0.00228 |
| Haiku 4.5 | $0.00007 | $0.00114 |
Grade A, and why
dev-standards 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 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.
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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Стандарт разработки
Базовые принципы (ВЫСШИЙ ПРИОРИТЕТ)
- Писать элегантный код, решающий задачу
- Не добавлять обратную совместимость без явного запроса
- После каждого блока кода: линтинг → компиляция → тесты → запуск
- Предпочитать правку существующего вместо добавления нового
- Качество превыше скорости — лучше потратить время на качественный код
- При неуверенности — спросить с озвучиванием рекомендаций
Метрики качества (ОБЯЗАТЕЛЬНО)
| Метрика | Лимит |
|---|---|
| Cyclomatic Complexity | < 10 |
| Длина функции | < 30 строк |
| Длина класса | < 200 строк |
| Параметры функции | < 5 (объект для >5) |
| Вложенность | < 4 уровней |
Правило 3-х альтернатив
- Придумать 3 решения
- Выбрать простейшее работающее
- Избегать первого пришедшего в голову
Code Review вопросы (ВСЕГДА задавать себе)
- "Можно ли это сделать проще?"
- "Зачем эта сложность?" (для функций >30 строк)
- "Есть ли стандартное решение?"
- "Понятно ли junior разработчику?"
Стоп-сигналы сложности 🚨
Остановиться и пересмотреть решение при:
- "Это очень умное решение" 🚩
- "Только я понимаю как это работает" 🚩
- "Потом разберёмся" 🚩
- "Тут нужно быть осторожным" 🚩
- Требуется объяснение одного и того же 2+ раза 🚩
Анти-паттерны (ИЗБЕГАТЬ)
- Преждевременная абстракция — абстрагировать только при реальном дублировании
- Generic hell — избегать
T<K<V<U>>> - God-функции — функция делает >3 разных вещей
- Callback ад — >3 уровней вложенности callbacks
- Магические значения — числа/строки без объяснения
Триггеры рефакторинга
| Ситуация | Действие |
|---|---|
| Дебаг >30 мин | Упростить код |
| Тест сложнее кода | Упростить код |
| Страшно менять | Упростить архитектуру |
| Повторяешь объяснение | Добавить комментарий или упростить |
Процесс работы с пользователем
- Обсуждение → исследовать варианты → уточняющие вопросы
- ТЗ → сформулировать → разбить на задачи → получить подтверждение
- Реализация → спросить "Приступаем к реализации?" → дождаться подтверждения
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 121 lines · 74 tokens per session scan A c299f192b126
dev-standards is a skill published in the GitHub repository weselow/Yandex-webmaster-mcp-server (6 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 1,142 once invoked, about $0.0003 per session on Opus 5.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 skills, from other repositories
adk-go-self-review
Review an ADK Go change the way a maintainer will — a fresh-context pass over the whole diff, five lenses (correctness and tests, scope, simplicity, style, adk-python parity), and the mutation check that proves your tests pin the change. Use before opening a PR, before any later push that changes code, and when asked…
software-test-review
Evaluate the quality of TDD tests against slice acceptance criteria, codebase conventions, and Red-phase execution results, producing a structured review with Accept or Revise recommendations. Use when tests written during the Red phase of red-green-refactor need quality review — checking coverage of acceptance…
software-code-refactoring
Improve production code quality while preserving all existing test behavior. Commonly used for the Refactor phase of TDD red-green-refactor, but applicable to any codebase with tests. Use when production code works but needs cleanup — reducing duplication, improving naming, simplifying complexity, aligning with…
ring:running-dev-cycle
Running the backend dev cycle: implements every task in a rolling-wave plan.md (ring:writing-plans format) for a Go/TS service, driving specialist agents through Gate 0 implementation/TDD, Gate 8 parallel review, and Gate 9 validation per epic, elaborating later phases at each phase boundary. Use when starting or…
ring:instrumenting-streaming-events
Instrumenting streaming events: wires lib-streaming event emission end-to-end into a Lerian Go service via a 13-gate cycle (catalog, Builder bootstrap, Emit sites, outbox, HTTP manifest, NoopEmitter fallback, integration and chaos tests), dispatching ring:backend-go under TDD. Consumes the validated…
ring:implementing-tasks
Implementing a single planned task (Task N.M.T) end-to-end: selects the right backend agent by language and service type, drives one TDD RED->GREEN turn, then verifies coverage, lint, license headers, runtime, and delivery before handoff. Runs as Gate 0 before ring:reviewing-code. Use to drive ONE task inside an…