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-zip-export-pitfalls)<a href="https://agentmods.dev/rules/desko77/cursor-1c-skills/edt-zip-export-pitfalls"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/edt-zip-export-pitfalls.svg" alt="Measured on agentmods" 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.01941 |
| Opus 5 | $0.00000 | $0.00971 |
| Sonnet 5 | $0.00000 | $0.00388 |
| Haiku 4.5 | $0.00000 | $0.00194 |
Grade A, and why
edt-zip-export-pitfalls 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 8d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EDT Zip Export Pitfalls
Грабли EDT при экспорте конфигурации в инфобазу (incremental sync через zip-архив).
Применяется: при создании/правке объектов метаданных в EDT-проектах (Configuration или Extension),
особенно через MCP edit_metadata / прямую правку .mdo. Касается агента разработчика mcp-edt.
Симптомы общие: EDT-валидация (get_project_errors) чистая, но при запуске/обновлении ИБ платформа
падает с RuntimeCoreException и сообщением Файл не обнаружен 'zip:///...'.
1. Подсистема с командным интерфейсом без CommandInterface.cmi
Симптом
Ошибка загрузки/выгрузки конфигурации
по причине:
Файл не обнаружен 'zip:///Ext/CommandInterface.xml'
Стек: DesignerSessionThickClientLauncher.importIncrementalXmlToInfobase →
LoadFilesQuery.processExecutionResponses.
Условие
Создана собственная подсистема (не Adopted) с <includeInCommandInterface>true</includeInCommandInterface>
в .mdo, но рядом нет файла CommandInterface.cmi.
Фикс
Создать минимальный CommandInterface.cmi рядом с .mdo подсистемы:
<?xml version="1.0" encoding="UTF-8"?>
<cmi:CommandInterface xmlns:cmi="http://g5.1c.ru/v8/dt/cmi"/>
Затем clean_project + revalidate_objects для подсистемы.
Когда применять профилактически
При создании любой новой собственной подсистемы расширения через edit_metadata create_object Subsystem,
если предполагается includeInCommandInterface=true - сразу создавать пустой CommandInterface.cmi.
В типовой конфигурации (без расширения) у части подсистем .cmi отсутствует и все работает - там
индекс EDT давно собран. Для свежедобавленных в расширение лучше создавать явно.
2. Профилактический чеклист при создании объекта метаданных через EDT MCP
Для агента разработчика mcp-edt - перед каждым update_database или запуском ИБ:
Subsystem (новая собственная)
-
<name>уникальное (с префиксом расширения, напр.Ext_*) -
<includeInCommandInterface>true</includeInCommandInterface>- обязателенCommandInterface.cmiрядом - Все ссылки
<content>указывают на существующие объекты конфигурации - Объект зарегистрирован в
Configuration.mdo(<subsystems>Subsystem.Имя</subsystems>)
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.
- 8d ago First seen · 146 lines · 0 tokens per session scan A b67abd506ca5
edt-zip-export-pitfalls is a cursor rule published in the GitHub repository Desko77/cursor-1c-skills (55 stars, last pushed 6d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,941 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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.