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.
npx skills add Desko77/cursor-1c-skills --skill 1c-rls-perf-connectgit clone --depth 1 https://github.com/Desko77/cursor-1c-skillsWrote 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/skills/desko77/cursor-1c-skills/1c-rls-perf-connect)<a href="https://agentmods.dev/skills/desko77/cursor-1c-skills/1c-rls-perf-connect"><img src="https://agentmods.dev/badge/skills/desko77/cursor-1c-skills/1c-rls-perf-connect/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/skills/desko77/cursor-1c-skills/1c-rls-perf-connect"><img src="https://agentmods.dev/badge/skills/desko77/cursor-1c-skills/1c-rls-perf-connect.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.00135 | $0.03773 |
| Opus 5.5 | $0.00054 | $0.01509 |
| Sonnet 5.5 | $0.00027 | $0.00755 |
| Haiku 4.5 | $0.00014 | $0.00377 |
Grade A, and why
1c-rls-perf-connect 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 today.
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.
This is a copy
100% identical to 1c-rls-perf-connect — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 224 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Подключение объекта к производительному RLS БСП
Производительный вариант ограничения доступа не разворачивает условие роли напрямую, а строит
предрассчитанные ключи доступа в регистрах КлючиДоступаКОбъектам и КлючиДоступаКРегистрам.
Текста ограничения недостаточно: объект должен входить в служебные структуры подсистемы, иначе
список не открывается.
Вариант работы: НСИ и администрирование - Настройки пользователей и прав - Группы доступа - Вариант
работы; программно - УправлениеДоступом.ПроизводительныйВариант. Вариант выбирает активную ветку
условия роли и сам по себе причиной падения списков не бывает. Шаги ниже выполняются и в стандартном
варианте: без них условие роли перестает разворачиваться после переключения варианта.
Смежные справочники набора:
| Вопрос | Где |
|---|---|
программный интерфейс УправлениеДоступом, наборы значений доступа, пересчет прав |
скил 1c-ssl-patterns, references/access-management.md |
| сигнатура и существование метода БСП | скил 1c-bsp-api |
профили групп доступа из кода, ЧтениеРазрешено, ЕстьРоль |
правило bsp-profile-rights-api.md |
| роль с условием и шаблонами в формате Конфигуратора | скилы 1c-role-compile, 1c-role-edit, 1c-role-validate |
Когда НЕ применять
- Ограничение делается отбором в форме, а не подсистемой доступа.
- Конфигурация без БСП или без подсистемы Управление доступом.
- Нужно раздать роли и права целиком, без ограничения по значениям: это профили групп доступа, не RLS.
Шаги
Роли и определяемые типы должны быть готовы до первого обновления доступа.
В EDT-проекте метаданные и модули правятся инструментами сервера ai-edt (каталог - скил
ai-edt-tools): BSL через write_module_source, метаданные через edit_metadata, перед
update_database - validate_for_export. В формате Конфигуратора - скилы 1c-cfe-*, 1c-meta-*,
1c-role-*.
1. Зарегистрировать список
В УправлениеДоступомПереопределяемый (в расширении - перехват &После, скил 1c-cfe-patch-method):
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.
- today First seen · 224 lines · 135 tokens per session scan A c8295a57b5a0
1c-rls-perf-connect is a skill published in the GitHub repository Desko77/cursor-1c-skills (69 stars, last pushed today), licensed MIT. It adds 135 tokens to every session and 3,773 once invoked, about $0.0005 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to 1c-rls-perf-connect, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
1c-rls-perf-connect
Instructions for connecting a new 1C object to the Business Application Development Library's record-level access system. Record-level access controls which users can see particular records, such as those for an organisation, warehouse, or department.
kd2-rules
A development guide for building data-exchange rules in 1C:Enterprise Data Conversion 2.0. This software maps objects and fields between two 1C configurations and exports the resulting rules as XML.
1c-db-cfe-admin
A command-line administrator for extensions already installed in a 1C information base, which is a 1C application's stored database and configuration. It uses ibcmd rather than the 1C development environment.
1c-meta-compile
A generator for creating 1C metadata objects from a JSON description. Metadata objects include parts of a 1C business configuration, such as catalogs, documents, registers, constants, modules, reports, and data processors.
1c-cf-new-project
A workflow for creating a new 1C configuration from an empty starting point. 1C is a platform for building business applications; a configuration defines their data, screens, permissions, and behavior.
1c-xdto-validate
A checker for 1C XDTO packages and their connection to a configuration. It reports errors that could make 1C reject the package or interpret its data incorrectly at runtime.