What is bsl-method-description?

A style guide for writing documentation comments on 1C methods. It defines the repository's required sections, formatting, method references, type names, examples, and line length.

Use it when adding or editing 1C method comments, especially comments for exported methods and parameters represented by structured values.

It prevents comments that do not match the project's conventions or point to methods that do not exist. That makes generated or maintained API documentation more reliable.

How bia-technologies/yaxunit configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to bia-technologies/yaxunit. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/bia-technologies/yaxunit/develop/.agents/skills/bsl-method-description/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/bia-technologies/yaxunit

Made for: Claude Code, Codex.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/bia-technologies/yaxunit/bsl-method-description/github.svg)](https://agentmods.dev/skills/bia-technologies/yaxunit/bsl-method-description)

Your own site

<a href="https://agentmods.dev/skills/bia-technologies/yaxunit/bsl-method-description"><img src="https://agentmods.dev/badge/skills/bia-technologies/yaxunit/bsl-method-description/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/bia-technologies/yaxunit/bsl-method-description"><img src="https://agentmods.dev/badge/skills/bia-technologies/yaxunit/bsl-method-description.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 635 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.

Model	Per session	Once invoked
Fable 5.1	$0.00044	$0.00635
Opus 5.5	$0.00018	$0.00254
Sonnet 5.5	$0.00009	$0.00127
Haiku 4.5	$0.00004	$0.00064

Measured yesterday against content hash dd119552e707, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bsl-method-description 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 yesterday.

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.

.agents/skills/bsl-method-description/SKILL.md · 52 lines

What it actually says

Нестандартные правила док-комментариев (базовый формат 1С считается известным)

Базовый стандарт (секции Параметры: / Возвращаемое значение: / Пример:, формат Имя - Тип - Описание, Массив из Тип) не пересказывается. Ниже — только уточнения и нестандартные элементы.

Общие правила

Не пиши комментарий, если он не добавляет полезной информации; для простых методов с очевидным назначением описание можно опустить.
Между секциями комментария — пустая строка.
Описание размещается перед директивой условной компиляции, если она есть.
В описаниях параметров вместо типа «Структура» указывай ссылку на метод-конструктор (см. ниже), для этого анализируй кодовую базу решения.
После генерации описаний проверь все ссылки на методы — существуют ли они.
Для экспортных методов в примере должно быть имя модуля.
Тип общего модуля указывается в формате CommonModule.<Имя модуля>.
Длина строки — не более 120 символов.

Ссылки на методы-конструкторы («см.»)

Для параметров-структур/ТЗ и возвращаемых значений не разворачивай поля, а ссылайся:

// Параметры:
//   ТекущаяСтрока - СтрокаТабличнойЧасти - строка табличной части документа.
//   ПараметрыЗаполненияЦен - см. ЦенообразованиеСервер.ПараметрыЗаполненияЦен
//
// Возвращаемое значение:
//   Структура - см. ЦенообразованиеСервер.ПараметрыЗаполненияЦен
//
Функция ПараметрыЗаполненияЦен() Экспорт

//   Запросы - см. Обработка.КонсольЗапросов.ТабличнаяЧасть.Запросы
//   Возвращаемое значение:
//     Массив из см. ОбновлениеИнформационнойБазы.ПараметрыОбновления

Маркер «+» для списков внутри описания параметра

Если в описании параметра нужен маркированный список — используй + (а не *):

// Параметры:
//   НесколькоНастроек - Массив - со значениями:
//     + Значение - Структура - со свойствами:
//         * Объект    - Строка
//         * Настройка - Строка
//         * Значение  - Произвольный

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.

yesterday First seen · 52 lines · 44 tokens per session scan A dd119552e707

Subscribe to this mod's changes

bsl-method-description is a skill published in the GitHub repository bia-technologies/yaxunit (342 stars, last pushed yesterday), licensed Apache-2.0. It adds 44 tokens to every session and 635 once invoked, about $0.0002 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-10-28.

1c-enterprise Testing Unit testing Writing and docs hacktoberfest hacktoberfest2022 yaxunit

author-test

Generate a test given sample. Parameters: C# SDK repository root; Package name: one of Azure.AI.Projects, Azure.AI.Projects.Agents or Azure.AI.Extensions.OpenAI; the sample to use as a starting point for the test.

Azure/azure-sdk-for-net · 68 tokens

edt-mcp-project-yaxunit

Discover, run, debug, poll, and cancel YAXUnit tests through current EDT-MCP launch and background-job contracts. Not for generic UI tests.

DitriXNew/EDT-MCP · 39 tokens

test-writing

A guide for writing YaxUnit tests, including test doubles called mocks and checks called assertions, for BSL code.

SteelMorgan/1c-agent-based-dev-framework · 17 tokens

yaxunit-isolation

A testing skill for YaxUnit database-writing tests that uses transactions. A transaction groups database changes so they can be handled as one unit during a test.

SteelMorgan/1c-agent-based-dev-framework · 15 tokens

1c-test-runner

A testing skill for running and writing unit tests for 1C modules, including verification through the 1C debugging tools.

Arman-Kudaibergenov/1c-ai-development-kit · 88 tokens

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

yaxunit: Skill for Claude Code