agentmods.dev

1c-bsl-runtime-specifics

1c-bsl-runtime-specifics is a cursor rule for Cursor from Desko77/cursor-1c-skills. It costs 0 tokens per session (2,049 once invoked), scanned A, original, MIT.

A set of rules for finding runtime errors in BSL, the programming language used by 1C, that static code checks may miss. It includes examples involving collections, types, transactions, and managed locks.

In plain words
What is it for?
Use it while writing or reviewing BSL code, especially when investigating type errors and other execution-time failures.
Why use it?
It highlights mistakes that can pass the editor's validation but fail when the program actually runs.

Cursor rule for Cursor

Written for Cursor: a Cursor rule (.mdc).

not rated 70repo +1 4d ago A scan 0 tokens original MIT

Good fit Use it while writing or reviewing BSL code, especially when investigating type errors and other execution-time failures.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/desko77/cursor-1c-skills/1c-bsl-runtime-specifics
View source ↗ Desko77/cursor-1c-skills
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.

Clone the repo
git clone --depth 1 https://github.com/Desko77/cursor-1c-skills

Made for: Cursor.

Wrote 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.

agentmods badge for 1c-bsl-runtime-specifics

README.md
[![agentmods](https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/1c-bsl-runtime-specifics/github.svg)](https://agentmods.dev/rules/desko77/cursor-1c-skills/1c-bsl-runtime-specifics)
Your own site
<a href="https://agentmods.dev/rules/desko77/cursor-1c-skills/1c-bsl-runtime-specifics"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/1c-bsl-runtime-specifics/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.

agentmods 80×15 button for 1c-bsl-runtime-specifics

Your own site · 80×15
<a href="https://agentmods.dev/rules/desko77/cursor-1c-skills/1c-bsl-runtime-specifics"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/1c-bsl-runtime-specifics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,049 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00000 $0.02049
Opus 5.5 $0.00000 $0.00820
Sonnet 5.5 $0.00000 $0.00410
Haiku 4.5 $0.00000 $0.00205

Measured 4d ago against content hash 2de60331d42c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

1c-bsl-runtime-specifics 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 4d 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.

rules/1c-bsl-runtime-specifics.mdc · 103 lines

How it starts

The opening of the file, as written. The whole thing — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Особенности выполнения BSL, которые не видит статический анализ

Применяется: при написании и ревью кода BSL. Описанные ошибки проходят валидацию EDT и проявляются только при выполнении.

Транзакции и управляемые блокировки - 1c-transactions-and-locks.md, каталог дефектов - anti_patterns.md.

Коллекции и типы

  • Объект.ДополнительныеСвойства - Структура, а не Соответствие: .Свойство("Ключ"), а не .Получить() (ошибка выполнения).
  • ПрочитатьJSON(Чтение, Истина) возвращает Соответствие (метода .Свойство нет), без флага - Структура. У ОбщегоНазначения.JSONВЗначение второй параметр - ИменаСвойствСоЗначениямиДата, третий - ПрочитатьВСоответствие.
  • .Выгрузить() и .Скопировать(): поле строки Выгрузить()[0], соответствующее вложенной табличной части (Таблица.(...) КАК ВложеннаяТЧ), - ТаблицаЗначений: у него есть .Скопировать() и нет .Выгрузить(). Ошибка "Метод не обнаружен" при выполнении; статический анализ ее не находит, потому что тип поля произвольный.
  • У ДокументОбъект и строки табличной части нет метода .Свойство() - он есть у Структура, ФиксированнаяСтруктура, ДанныеФормыСтруктура.
  • Для X = 5 По 0 выполняет ноль итераций (счетчик только возрастает) - обратный обход через Пока Индекс >= 0.
  • Нет динамического вызова Модуль[ИмяМетода](Параметры) - явный Если / ИначеЕсли. Вычислить() и Выполнить() медленны и небезопасны.

Режимы и блокировки

  • УстановитьПривилегированныйРежим(Ложь) без парного (Истина) в той же процедуре завершается ошибкой (счетчик ведется по процедуре), и ошибка маскируется в Исключение. Восстанавливать режим по сохраненному флагу. ПривилегированныйРежим() возвращает состояние всего стека вызовов, для этой проверки не подходит.
  • УстановитьВремяОжиданияБлокировкиДанных() - административный метод (монопольный доступ к ИБ, сеанс без разделителей), а не таймаут конкретной управляемой блокировки. Из прикладного кода дает "База заблокирована". Управляемые блокировки ждут глобальный таймаут сами.
  • Управляемую блокировку документа или справочника ставить только по Ссылка: реквизиты, включая Номер, в пространстве блокировок недоступны. Защита от дублей при параллельном создании по бизнес-ключу - блокировка по значению измерения регистра-семафора (запись в регистр не нужна).

Read the full file on GitHub · 103 lines

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. 4d ago First seen · 103 lines · 0 tokens per session scan A 2de60331d42c

Subscribe to this mod's changes

1c-bsl-runtime-specifics is a cursor rule published in the GitHub repository Desko77/cursor-1c-skills (70 stars, last pushed 4d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,049 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-10-27.

1c1c-edt1c-enterpriseCode GenerationCode reviewDebuggingai-agentbsl
Related

Other cursor rules, from other repositories

jsdoc

A set of JSDoc rules for documenting JavaScript or TypeScript code, with comments written in Russian.

yellow-hammer/mcp-1c-platform-tools · 627 tokens

project-context

Technical context for a VS Code extension that exposes 1C Platform Tools to AI agents through an MCP server. The extension communicates with the standalone server over IPC, while the server registers one agent tool for each available 1C command.

yellow-hammer/mcp-1c-platform-tools · 1,169 tokens

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.

yellow-hammer/mcp-1c-platform-tools · 331 tokens

naming-abbreviations

A set of project rules for naming 1C Platform Tools and its MCP tools. It defines allowed short forms and limits the combined server and tool name to 60 characters.

yellow-hammer/mcp-1c-platform-tools · 277 tokens

evolution-no-legacy

A coding rule for changing software interfaces and configuration names without keeping old names working by default.

yellow-hammer/mcp-1c-platform-tools · 147 tokens

ponytail

Ponytail, lazy senior dev mode. Always pick the simplest solution that works.

DietrichGebert/ponytail · 604 tokens