agentmods.dev

1c-exchange-specifics

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

A set of practical rules for building data exchanges in 1C, a business software platform. It covers EnterpriseData, HTTP connections between systems, and communication between 1C databases.

In plain words
What is it for?
Use it when developing or reviewing integrations between 1C databases and external systems, including EnterpriseData packages and web-service exchanges.
Why use it?
It helps avoid format, identifier, and data-export errors that may only appear when an exchange runs.

Cursor rule for Cursor

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

not rated 69repo +1 2d ago A scan 0 tokens original MIT

Good fit Use it when developing or reviewing integrations between 1C databases and external systems, including EnterpriseData packages and web-service exchanges.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/desko77/cursor-1c-skills/1c-exchange-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-exchange-specifics

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

Your own site · 80×15
<a href="https://agentmods.dev/rules/desko77/cursor-1c-skills/1c-exchange-specifics"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/1c-exchange-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 984 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.00984
Opus 5.5 $0.00000 $0.00394
Sonnet 5.5 $0.00000 $0.00197
Haiku 4.5 $0.00000 $0.00098

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

Security

Grade A, and why

1c-exchange-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-exchange-specifics.mdc · 56 lines

How it starts

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

Особенности обменов 1С: EnterpriseData, НСИ, межбазовые запросы

Применяется: при разработке обменов - формат EnterpriseData (КД 3.1), обмен НСИ с внешней системой по HTTP, онлайн-обмен между базами, получение данных из другой базы через веб-сервис.

Правила КД 2.0 и работа с ними через 1c-mcp-toolkit - скил kd2-rules, правила КД 3.1 и расширение формата - скил kd31-rules.

EnterpriseData и собственные пакеты XDTO

  • Тип строки табличной части в расширении формата - всегда отдельный именованный тип (Документ.X.Товары.Строка), а не анонимный.
  • Неиспользуемые <import> в собственном пакете XDTO приводят к отказу XdtoExporter при update_database из EDT; Конфигуратор такие импорты разрешает, поэтому применение через Конфигуратор проходит.

Обмен НСИ с внешней системой

  • Соответствия объектов хранить ссылкой (ЛюбаяСсылка), а не строкой кода. Новый УникальныйИдентификатор("00-000043") завершается ошибкой на строке не в формате UUID, и появляются дубли. Образец - регистр БСП ПубличныеИдентификаторыСинхронизируемыхОбъектов. Для уже накопленных строковых значений - функция "сначала UUID, затем НайтиПоКоду".
  • Строка GUID -> ссылка: Справочники.X.ПолучитьСсылку(Новый УникальныйИдентификатор(GUID)) в Попытка.
  • При расхождении спецификации (JSON-контракт) и реальных данных верна версия данных: регистр ключей JSON (Id и id), имена значений перечислений и выбор "перечисление или строка" не совпадают со спецификацией. Имена значений перечислений - из .mdo, реальный JSON - из журнала регистрации или журнала обмена.
  • Внешний веб-интерфейс может ожидать строковые имена типов в JSON (attributeType: "Code", entityType: "Regular", action: "Create"), а не числовые коды. Значения перечисления брать из клиентского кода интерфейса, а не из документации.
  • HTTP-сервис: бизнес-ошибки - на языке оператора (русский для складских систем и ТСД), технические идентификаторы - латиницей.
  • Онлайн-обмен периферии с центром без РИБ: HTTP-сервис на центральной базе и расширение в периферийной (подписки на запись, очередь с отложенной отправкой, HTTP-клиент), формат JSON, аутентификация по токену.

Read the full file on GitHub · 56 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. 2d ago First seen · 56 lines · 0 tokens per session scan A fb4d3820063a

Subscribe to this mod's changes

1c-exchange-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 984 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-enterpriseBackend and APIsCode GenerationDebuggingai-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 · 644 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 · 959 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

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 · 307 tokens

ponytail

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

DietrichGebert/ponytail · 604 tokens

angular-20

This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.

angular/angular · 0 tokens