external-data-source-mdo

external-data-source-mdo is a cursor rule for coding agents from Desko77/cursor-1c-skills. It costs 0 tokens per session (2,791 once invoked), scanned A, original, MIT.

A file-format guide for defining external data sources in 1C:Enterprise Development Tools (1C:EDT), an environment for building 1C business applications. It describes the folders and XML metadata files used for these sources.

In plain words
What is it for?
Use it when creating or reviewing 1C:EDT ExternalDataSource metadata, including its root file, tables, produced types, and table fields.
Why use it?
It prevents the table fields and metadata from being placed in the wrong files or directories. This matters because external data sources use a different layout from some other 1C metadata types.

Cursor rule

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.

agentmods
npx agentmods add rules/desko77/cursor-1c-skills/external-data-source-mdo
Clone the repo
git clone --depth 1 https://github.com/Desko77/cursor-1c-skills

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 external-data-source-mdo

README.md
[![agentmods](https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/external-data-source-mdo.svg)](https://agentmods.dev/rules/desko77/cursor-1c-skills/external-data-source-mdo)
Your own site
<a href="https://agentmods.dev/rules/desko77/cursor-1c-skills/external-data-source-mdo"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/external-data-source-mdo.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 2,791 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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 $0.00000 $0.02791
Opus 5 $0.00000 $0.01396
Sonnet 5 $0.00000 $0.00558
Haiku 4.5 $0.00000 $0.00279

Measured 4d ago against content hash 39ab5d16aa73, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

external-data-source-mdo 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/external-data-source-mdo.mdc · 292 lines

How it starts

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

ExternalDataSource MDO Format (EDT)

Правила создания и работы с внешними источниками данных (ВИД) в формате EDT.

Применяется: при создании ExternalDataSource MDO-файлов в проектах 1C:EDT.


Структура файлов

src/ExternalDataSources/<ИмяВИД>/
  <ИмяВИД>.mdo                          ← Корневой MDO внешнего источника
  Tables/
    <ИмяТаблицы1>/
      <ИмяТаблицы1>.mdo                 ← MDO таблицы (поля ВНУТРИ файла)
    <ИмяТаблицы2>/
      <ИмяТаблицы2>.mdo

Важно: Поля таблицы (tableFields) описываются ВНУТРИ MDO-файла таблицы - НЕ как отдельные файлы. Это отличает ExternalDataSource от справочников/документов, где реквизиты - отдельные файлы.


Корневой MDO - ExternalDataSource

<?xml version="1.0" encoding="UTF-8"?>
<mdclass:ExternalDataSource xmlns:mdclass="http://g5.1c.ru/v8/dt/metadata/mdclass" uuid="<UUID>">
  <producedTypes>
    <managerType typeId="<UUID>" valueTypeId="<UUID>"/>
    <tablesManagerType typeId="<UUID>" valueTypeId="<UUID>"/>
    <cubesManagerType typeId="<UUID>" valueTypeId="<UUID>"/>
  </producedTypes>
  <name>ИмяВИД</name>
  <synonym>
    <key>ru</key>
    <value>Синоним ВИД</value>
  </synonym>
  <dataLockControlMode>Managed</dataLockControlMode>
  <tables>ExternalDataSource.ИмяВИД.Table.ИмяТаблицы1</tables>
  <tables>ExternalDataSource.ИмяВИД.Table.ИмяТаблицы2</tables>
</mdclass:ExternalDataSource>

producedTypes

ExternalDataSource имеет 3 типа (НЕ путать с Table, у которой 8):

  • managerType - менеджер ВИД
  • tablesManagerType - менеджер таблиц
  • cubesManagerType - менеджер кубов

MDO таблицы - Table

<?xml version="1.0" encoding="UTF-8"?>
<mdclass:Table xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:core="http://g5.1c.ru/v8/dt/mcore" xmlns:mdclass="http://g5.1c.ru/v8/dt/metadata/mdclass" uuid="<UUID>">
  <producedTypes>
    <refType typeId="<UUID>" valueTypeId="<UUID>"/>
    <listType typeId="<UUID>" valueTypeId="<UUID>"/>
    <objectType typeId="<UUID>" valueTypeId="<UUID>"/>
    <managerType typeId="<UUID>" valueTypeId="<UUID>"/>
    <recordManagerType typeId="<UUID>" valueTypeId="<UUID>"/>
    <recordSetType typeId="<UUID>" valueTypeId="<UUID>"/>
    <recordType typeId="<UUID>" valueTypeId="<UUID>"/>
    <recordKeyType typeId="<UUID>" valueTypeId="<UUID>"/>
  </producedTypes>
  <name>ИмяТаблицы</name>
  <synonym>
    <key>ru</key>
    <value>Синоним таблицы</value>
  </synonym>
  <parentDataSource>ExternalDataSource.ИмяВИД</parentDataSource>
  <nameInDataSource>&quot;ИмяТаблицыВБД&quot;</nameInDataSource>
  <keyFields>ExternalDataSource.ИмяВИД.Table.ИмяТаблицы.Field.КлючевоеПоле</keyFields>
  <unfilledParentValue xsi:type="core:UndefinedValue"/>
  <useStandardCommands>true</useStandardCommands>
  <transactionsIsolationLevel>ReadUncommitted</transactionsIsolationLevel>
  <editType>InDialog</editType>
  <dataLockControlMode>Managed</dataLockControlMode>
  <!-- Поля таблицы (tableFields) идут далее -->
</mdclass:Table>

Read the full file on GitHub · 292 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 · 292 lines · 0 tokens per session scan A 39ab5d16aa73

Subscribe to this mod's changes

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