What is 1c-skd-specifics?

A set of rules for 1C reports built with the Data Composition System, which turns queries and settings into formatted reports. It covers report schemas, filters, temporary tables, parameters, and tabular output.

Use it when editing .dcs report schemas, writing report queries, setting filters and parameters in code, handling two-pass report generation, or sending results to a table document.

It prevents filters from being applied in the wrong query layer, fields from disappearing, and virtual-table reports from returning incorrect or inefficient results.

1c-skd-specifics — Cursor rule for Cursor by 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/1c-skd-specifics/github.svg)](https://agentmods.dev/rules/desko77/cursor-1c-skills/1c-skd-specifics)

Your own site

<a href="https://agentmods.dev/rules/desko77/cursor-1c-skills/1c-skd-specifics"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/1c-skd-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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/desko77/cursor-1c-skills/1c-skd-specifics"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/1c-skd-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 1,291 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.00000	$0.01291
Opus 5.5	$0.00000	$0.00516
Sonnet 5.5	$0.00000	$0.00258
Haiku 4.5	$0.00000	$0.00129

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

Security

Grade A, and why

1c-skd-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 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.

rules/1c-skd-specifics.mdc · 68 lines

How it starts

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

Особенности СКД и отчетов 1С

Применяется: при доработке отчетов на СКД - схема .dcs, модуль отчета, программная компоновка, вывод в табличный документ.

Двухпроходная компоновка, набор-объект в файле схемы, параметры-выражения и МакетКомпоновки.ЗначенияПараметров - 1c-skd-two-pass-preprocessing.md. Выполнение запроса отчета без компоновки - 1c-report-direct-query.md.

Отборы и поля в тексте запроса

{ГДЕ} и программные отборы СКД подставляются во ВСЕ временные таблицы пакета с тем же псевдонимом, а не только в итоговый запрос. Поля, вычисленные на уровне документа, теряют ветки ОБЪЕДИНИТЬ. Защита: расчетным полям во временных таблицах давать префикс (Расч_), в итоговом запросе ссылаться на них, {ГДЕ} писать по исходным псевдонимам итогового запроса.
{ВЫБРАТЬ} ищет поля по реальным именам таблиц, а не по псевдонимам КАК - оборачивать поле в ВЫБОР КОГДА ... КОНЕЦ КАК X.
Отборы СКД ({ГДЕ}) не подставляются в параметры виртуальных таблиц (.Остатки, .Обороты) - фильтр внутри виртуальной таблицы задается только через &Параметр (УстановитьПараметр).
Оптимизатор СКД удаляет поля, вычисленные ВЫРАЗИТЬ во временной таблице, если их нет в выводе: под ограниченной ролью колонка пропадает. Перевести поле на разыменование (Регистратор.Номер) в выражении поля СКД - оно вычисляется при выводе, а не в SQL, поэтому точка здесь допустима, в отличие от SQL под RLS.

Схема .dcs

Типы полей набора-объекта (DataSetObject) в .dcs: Number - xs:decimal с Digits / FractionDigits (не Precision / Scale, это формат .mdo); String - StringQualifiers / Length; Date - xs:dateTime с DateFractions; ссылка - через пространство имен current-config (d4p1:CatalogRef.X).
userSettingID допустим только в отдельном userSettings на уровне settingsVariant, а не внутри SettingsParameterValue.
В закомментированных строках запроса в .dcs - только <>, а не <>.
Схема без <dataSet> (только параметры и settingsVariant) - допустимая схема: данные передаются через ВнешниеНаборыДанных в коде. Набор данных в нее не добавлять.

Read the full file on GitHub · 68 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.

2d ago First seen · 68 lines · 0 tokens per session scan A 3f81a9aa90ae

Subscribe to this mod's changes

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

1c 1c-edt 1c-enterprise Analytics and metrics Backend and APIs Code Generation ai-agent bsl

1c-skd-specifics

Getting it into your agent

Wrote this? Show the measurements

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Особенности СКД и отчетов 1С

Отборы и поля в тексте запроса

Схема .dcs

What this file has done since we first saw it

Other cursor rules, from other repositories

jsdoc

project-context

naming-abbreviations

code-style

evolution-no-legacy

ponytail