code-style

Project rules for code style, commit messages, comments, interface text, logs, TypeScript, and documentation. They require Russian text in user-facing and code-comment contexts, along with strict TypeScript practices.

In plain words
What is it for?
Writing Conventional Commit messages in Russian, naming and typing TypeScript code, documenting exported code, formatting logs and UI messages, and removing debug output before commits.
Why use it?
They keep contributions consistent across the project and reduce avoidable type and maintenance problems. They also define checks to perform before committing code.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/yellow-hammer/mcp-1c-platform-tools/code-style
Clone the repo
git clone --depth 1 https://github.com/yellow-hammer/mcp-1c-platform-tools

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 307 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.00307
Opus 5 $0.00000 $0.00153
Sonnet 5 $0.00000 $0.00061
Haiku 4.5 $0.00000 $0.00031

Measured 2d ago against content hash 26c1fe0c2460, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

code-style 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 2d 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.

.cursor/rules/code-style.mdc · 35 lines

What it actually says

Стиль кода и коммиты

Коммиты

  • Conventional Commits: префиксы feat:, fix:, docs:, chore:, refactor: и т.д.
  • Сообщения коммитов — на русском.

Язык в коде и интерфейсе

  • Комментарии в коде: на русском.
  • Сообщения пользователю (showInformationMessage, showErrorMessage, текст в UI): на русском.
  • Строки для логов: на русском.

TypeScript

  • Строгий режим (tsconfig), импорты Node с префиксом node: где уместно.
  • Избегать any; использовать типы из @types/vscode, @types/node.

JSDoc

  • Документировать экспортируемые сущности и модули; комментарии на русском.
  • Подробные правила — в jsdoc.mdc.

Перед коммитом

  • Удалять отладочный вывод и лишние комментарии.

Эволюция: .cursor/rules/evolution-no-legacy.mdc.

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. 2d ago First seen · 35 lines · 307 tokens per session scan A 26c1fe0c2460

Subscribe to this mod's changes

code-style is a cursor rule published in the GitHub repository yellow-hammer/mcp-1c-platform-tools (35 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 307 tokens. 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-30.