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/query-optimization-tips)<a href="https://agentmods.dev/rules/desko77/cursor-1c-skills/query-optimization-tips"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/query-optimization-tips/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/query-optimization-tips"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/query-optimization-tips.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.02640 |
| Opus 5.5 | $0.00000 | $0.01056 |
| Sonnet 5.5 | $0.00000 | $0.00528 |
| Haiku 4.5 | $0.00000 | $0.00264 |
Grade A, and why
query-optimization-tips 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 21d 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 — 242 lines — stays where its author put it; the contents beside it link to each section on GitHub.
1C Query Optimization Tips
Полезные советы по оптимизации запросов 1С (стандарты ИТС).
Применяется: при написании и ревью запросов 1С.
Анти-паттерны производительности - карточки PERF-01, PERF-02, PERF-03 каталога дефектов (скил 1c-code-review); советы этого файла перенесены в карточки QUERY-04 - QUERY-12. Продвинутые паттерны (временные таблицы, пакетные запросы, СКД) - см. скил /1c-query-optimization.
Составные типы - ВЫРАЗИТЬ
Обращение через точку к полям составного типа (напр. Регистратор) создает соединения со ВСЕМИ возможными типами. Используй ВЫРАЗИТЬ для указания конкретного типа.
// Плохо: обращение к полю Регистратора без ВЫРАЗИТЬ - JOIN со ВСЕМИ типами регистраторов
"ВЫБРАТЬ
| ТоварыНаСкладах.Регистратор.Дата КАК ДатаДокумента
|ИЗ
| РегистрНакопления.ТоварыНаСкладах КАК ТоварыНаСкладах"
// Хорошо: указан конкретный тип
"ВЫБРАТЬ
| ВЫРАЗИТЬ(ТоварыНаСкладах.Регистратор КАК Документ.ПоступлениеТоваровУслуг).Дата КАК ДатаДокумента
|ИЗ
| РегистрНакопления.ТоварыНаСкладах КАК ТоварыНаСкладах"
// Для нескольких типов - ВЫБОР/КОГДА
"ВЫБРАТЬ
| ВЫБОР
| КОГДА ТоварыНаСкладах.Регистратор ССЫЛКА Документ.ПоступлениеТоваровУслуг
| ТОГДА ВЫРАЗИТЬ(ТоварыНаСкладах.Регистратор КАК Документ.ПоступлениеТоваровУслуг).Дата
| КОГДА ТоварыНаСкладах.Регистратор ССЫЛКА Документ.РеализацияТоваровУслуг
| ТОГДА ВЫРАЗИТЬ(ТоварыНаСкладах.Регистратор КАК Документ.РеализацияТоваровУслуг).Дата
| КОНЕЦ КАК ДатаДокумента
|ИЗ
| РегистрНакопления.ТоварыНаСкладах КАК ТоварыНаСкладах"
ПРЕДСТАВЛЕНИЕ вместо .Наименование
Когда нужно только текстовое представление ссылки, ПРЕДСТАВЛЕНИЕ() избегает лишнего соединения.
// Плохо: создает дополнительный подзапрос к Справочник.Склады
"ВЫБРАТЬ
| ТоварыНаСкладах.Склад.Наименование
|ИЗ
| РегистрНакопления.ТоварыНаСкладах КАК ТоварыНаСкладах"
// Хорошо: без лишнего соединения
"ВЫБРАТЬ
| ПРЕДСТАВЛЕНИЕ(ТоварыНаСкладах.Склад) КАК СкладПредставление
|ИЗ
| РегистрНакопления.ТоварыНаСкладах КАК ТоварыНаСкладах"
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.
- 21d ago Changed 1eb6e30af2a1
- 1mo ago First seen · 242 lines · 0 tokens per session scan A c77581959c2b
query-optimization-tips is a cursor rule published in the GitHub repository Desko77/cursor-1c-skills (69 stars, last pushed 12d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,640 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
jsdoc
A set of JSDoc rules for documenting JavaScript or TypeScript code, with comments written in Russian.
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.
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.
evolution-no-legacy
A coding rule for changing software interfaces and configuration names without keeping old names working by default.
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.