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.
git 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/rules/desko77/cursor-1c-skills/edt-form-xml-requirements)<a href="https://agentmods.dev/rules/desko77/cursor-1c-skills/edt-form-xml-requirements"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/edt-form-xml-requirements/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/rules/desko77/cursor-1c-skills/edt-form-xml-requirements"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/edt-form-xml-requirements.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.00000 | $0.03166 |
| Opus 5 | $0.00000 | $0.01583 |
| Sonnet 5 | $0.00000 | $0.00633 |
| Haiku 4.5 | $0.00000 | $0.00317 |
Grade A, and why
edt-form-xml-requirements 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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 278 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Требования EDT к XML-формам (Form.form)
Требования к формату Form.form, которые EDT предъявляет сверх того, что MCP-генератор обрабатывает автоматически.
Применяется: при генерации и ручной правке Form.form в EDT-проектах.
Что MCP-генератор обрабатывает автоматически
Не дублировать вручную - генератор уже добавляет:
- Типы:
String,Boolean,Number,Date(маппинг из xs:, cfg:, v8:) - Типы:
ExternalDataProcessor.(маппинг изExternalDataProcessorObject.) - visible/enabled/userVisible на всех элементах
- Свойства таблиц: changeRowSet, selectionMode, scrollbars, header/footer, drag (16 свойств)
- Companion-элементы таблиц: autoCommandBar, extendedTooltip, contextMenu, searchStringAddition, viewStatusAddition
- InputFieldExtInfo: chooseType, typeDomainEnabled, textEdit
- Колонки таблиц: editMode, showInHeader, headerHorizontalAlign, showInFooter
- Button type=UsualButton вне CommandBar
- Корневые свойства: autoTitle, autoUrl, autoFillCheck, enabled, showTitle, showCloseButton
Что генератор НЕ добавляет - нужно вручную
1. Root extInfo (обязательно для обработок/отчетов)
<extInfo xsi:type="form:ObjectFormExtInfo"/>
Тип зависит от владельца формы:
| Объект | xsi:type |
|---|---|
| Внешняя обработка / Обработка | form:ObjectFormExtInfo |
| Справочник | form:CatalogFormExtInfo |
| Документ | form:DocumentFormExtInfo |
| РегистрСведений | form:InformationRegisterFormExtInfo |
Без extInfo дизайнер EDT может показать пустую форму.
2. commandInterface
<commandInterface>
<navigationPanel/>
<commandBar/>
</commandInterface>
Требуется по Xcore-модели (FormCommandInterface[1]). EDT может добавить автоматически при сохранении, но лучше указать явно.
3. formCommands (команды формы)
Имя тега в EDT - <formCommands> (НЕ <commands> как в logform).
<formCommands>
<name>ИмяКоманды</name>
<id>100</id>
<action>ИмяОбработчика</action>
</formCommands>
4. ValueTable - columns с view/edit и уникальными <id>
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.
- 10d ago First seen · 278 lines · 0 tokens per session scan A d274eb6ef7a1
edt-form-xml-requirements is a cursor rule published in the GitHub repository Desko77/cursor-1c-skills (55 stars, last pushed 7d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,166 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.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.