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 skills add VKirill/claude-lane-stack --skill ru-checkgit clone --depth 1 https://github.com/VKirill/claude-lane-stackWrote 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/vkirill/claude-lane-stack/ru-check)<a href="https://agentmods.dev/skills/vkirill/claude-lane-stack/ru-check"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/ru-check/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/vkirill/claude-lane-stack/ru-check"><img src="https://agentmods.dev/badge/skills/vkirill/claude-lane-stack/ru-check.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.00076 | $0.02556 |
| Opus 5.5 | $0.00030 | $0.01022 |
| Sonnet 5.5 | $0.00015 | $0.00511 |
| Haiku 4.5 | $0.00008 | $0.00256 |
Grade A, and why
ru-check 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.
This is a copy
94% identical to ru-check — 22 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Russian Text Quality Check
Review the text provided in $ARGUMENTS (or the most recent Russian text output if no arguments) using the ru-text skill.
Where the reference files live
This skill reads the corpus that ships with the ru-text skill, which is installed alongside it. Locate that folder once, then read the named files from it:
- Look for a directory named
referenceswhose parent directory is namedru-text, and which containsinfo-style.md. Every file named below sits in that folder. - Search with file tools, never with a shell.
Globon a pattern like**/ru-text/references/info-style.md, or whatever file search the host offers, thenRead. This command has no use for a command line:Bashis on itsdisallowed-toolslist, and hosts that do not implement that field still refuse it — measured in Claude Cowork on 12.08.2026, where an openinglsreturned «Permission to use Bash has been denied» in red before the search found the corpus anyway. The call bought nothing and cost the reader a scare. - In Claude Code the plugin root is also available directly, which saves the search.
- Do not guess a path. If the folder cannot be found, say so and stop — a check run against remembered rules instead of the corpus is not this command, and reporting one as the other is the failure this whole product exists to prevent.
Two depths, one command
This check runs at one of two depths. Nobody chooses a depth; these rules do.
Full — the «Check order» below, whole. Run it whenever a person asked for this check («вычитай», «прогони ru-text», a gate that names ru-text, a golden-set run) or triage escalated. An explicit request is never answered with triage.
Triage — for self-initiated runs only: you produced or encountered Russian text and are checking it out of discipline, with no instruction naming ru-text. Load three things and nothing else:
- The ru-text
SKILL.md— its inline typography table and top stop-words. Skip if it is already in context, which on an always-on host it usually is. - The «Neuroslop index» section of
addenda.md: from the## Neuroslop indexheading to the next##. Not the rest of the file — the rest is ten times the size. - Section «B. Каталог стоп-слов» of
info-style.md: from its## B.heading to the next##. Not the rest of the file.
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 · 152 lines · 76 tokens per session scan A 043f7dec5d60
ru-check is a skill published in the GitHub repository VKirill/claude-lane-stack (122 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 2,556 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 94% identical to ru-check, differing in 22 lines, and is treated as a copy.
Other skills, from other repositories
build-teaql-app
Build or change a TeaQL application in Java, Rust, Go, Swift, Python, C#/.NET, or TypeScript, including Kotlin/JVM applications that consume Java-generated libraries. Mandatory order: first draft and save a complete KSML model, then verify the client and evaluate that saved model, repair it through repeated evaluation…
eval-agents
Audit custom subagent definitions for Claude Code (.claude/agents/.md) and Codex (.codex/agents/.toml): loadability against the native schema, description overlap, model tier, tool scope, and headless-safe instructions. Use when onboarding to a project with agents, after adding or importing agents, or when the parent…
self-assessment
Interactive skill assessment with personalized learning path generation.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
source-command-methodology-advisor
Analyzes your codebase and asks 3 targeted questions to recommend the right AI-assisted development methodology stack.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.