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.
git clone --depth 1 https://github.com/coddy-project/coddy-agentWrote 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/rules/coddy-project/coddy-agent/russian-wording)<a href="https://agentmods.dev/rules/coddy-project/coddy-agent/russian-wording"><img src="https://agentmods.dev/badge/rules/coddy-project/coddy-agent/russian-wording/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/rules/coddy-project/coddy-agent/russian-wording"><img src="https://agentmods.dev/badge/rules/coddy-project/coddy-agent/russian-wording.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.00410 | $0.00410 |
| Opus 5.5 | $0.00164 | $0.00164 |
| Sonnet 5.5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
russian-wording 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 21d 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.
What it actually says
Russian wording
The Russian adjective for "agent" / "agentic" is агентный (агентный режим, агентная сессия, агентные инструменты). Never write агентский: it is the wrong word for this meaning.
An agent that a session spawns is a субагент (субагент памяти, запускаю субагента, передать работу субагенту). Never write сабагент: the prefix is the Russian "суб-", as in "субподрядчик".
A git worktree keeps its English name, worktree (отдельный worktree, работает в worktree). Never translate it as рабочее дерево in any of its forms: nobody searches for the Russian calque, and the English word is what git, the chips of the composer and the documentation all say.
These rules apply to everything written in Russian for this project: the ru dictionary under
external/ui/src/ui/i18n/messages/, Russian documentation and screenshots of the Russian interface,
commit messages, issue comments and answers to the operator. The dictionary is held to them by
external/ui/src/ui/i18n/ruWording.test.ts. Before finishing a change that touches Russian text, run
the three checks below and expect no hits other than the rule files, which name the wrong words in
order to forbid them (the test spells them with a character class, so it stays out of the result):
git grep -n -i 'агентск'
git grep -n -i 'сабагент'
git grep -n -i -e 'рабочее дерево' -e 'рабочего дерева' -e 'рабочем дереве' -e 'рабочие деревья'
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.
- 21d ago Changed · +16 lines · +251 tokens per session 14495387f02f
- 1mo ago First seen · 14 lines · 159 tokens per session scan A 24f67df3aa98
russian-wording is a cursor rule published in the GitHub repository coddy-project/coddy-agent (175 stars, last pushed today), licensed MIT. It adds 410 tokens to every session, about $0.0016 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-09-13.
Other cursor rules, from other repositories
i18n
Multi-language content, translations, and localized templates.
sciclaw-papercuts
Papercuts from Sol/ImageMagick/release cycles — release, brew, CI, and workspace hygiene for sciClaw agents.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.