Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add skills/spumer/i-m-senior-developer/clarity-validatornpx skills add spumer/i-m-senior-developer --skill clarity-validatorgit clone --depth 1 https://github.com/spumer/i-m-senior-developerWrote 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/spumer/i-m-senior-developer/clarity-validator)<a href="https://agentmods.dev/skills/spumer/i-m-senior-developer/clarity-validator"><img src="https://agentmods.dev/badge/skills/spumer/i-m-senior-developer/clarity-validator.svg" alt="Measured on agentmods" 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 | $0.00174 | $0.02955 |
| Opus 5 | $0.00087 | $0.01477 |
| Sonnet 5 | $0.00035 | $0.00591 |
| Haiku 4.5 | $0.00017 | $0.00296 |
Grade A, and why
clarity-validator 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 5d 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 — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clarity Validator
Валидация консистентности текстов на основе FPF (A.7 Strict Distinction + A.10 Evidence Graph + A.1.1 BoundedContext + Intellect Stack). Выявляет смешение когнитивных слоёв, противоречия между файлами, скачки логики, терминологический дрифт и 12 специфичных для AI-авторов синтетических паттернов (negation of nothing, выдуманный флоу, leaked invariants, имитация авторитета через цифры и другие).
Когда запускать
| Триггер | Инициатор |
|---|---|
| После раунда ревью | оркестратор (проактивно) |
| Перед коммитом в docs-репозиторий | автор / оркестратор |
| После серии правок в нескольких файлах | автор / оркестратор |
| По запросу | пользователь |
Входные данные
Принимает один или несколько файлов:
- Один файл: полная проверка слоёв + логики + терминологии внутри файла
- Несколько файлов: дополнительно кросс-файловая проверка (консистентность + терминология между файлами)
- Директория: проверить все .md файлы в директории и связи между ними
Если файлы не указаны — спросить у вызывающего.
Пять проверок
1. Смешение когнитивных слоёв (Intellect Stack)
Каждая секция документа должна содержать утверждения одного когнитивного слоя:
| Слой | Вопрос | Маркеры |
|---|---|---|
| Structure | Из чего состоит? | Перечисления, определения, таблицы состава |
| Knowledge | Что наблюдаем? | «Показывает», «даёт сигнал о», факты, метрики |
| Action | Что делать? | Императивы: «задавай», «фиксируй», «не тестируй» |
| Strategy | Как выбирать? | «Если X → Y», правила решения, приоритеты |
| Governance | Кто решает? | Ответственные, процессы согласования, SLA |
Процедура проверки:
- Прочитать файл целиком
- Для каждой секции определить заявленный слой по заголовку
- Пройти по утверждениям, определить фактический слой каждого (тест: «могу наблюдать» = Knowledge, «должен сделать» = Action, «выбираю» = Strategy)
- Если заявленный ≠ фактический → находка
Подробные примеры и тесты: references/intellect-stack.md
What ships with it
4 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.
- 5d ago First seen · 215 lines · 174 tokens per session scan A 6f8cdbcbc772
clarity-validator is a skill published in the GitHub repository spumer/i-m-senior-developer (11 stars, last pushed 4d ago), licensed MIT. It adds 174 tokens to every session and 2,955 once invoked, about $0.0009 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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.
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…
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…