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.
npx agentmods add rules/desko77/cursor-1c-skills/forms_eventsgit 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/forms_events)<a href="https://agentmods.dev/rules/desko77/cursor-1c-skills/forms_events"><img src="https://agentmods.dev/badge/rules/desko77/cursor-1c-skills/forms_events.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 | $0.00000 | $0.00391 |
| Opus 5 | $0.00000 | $0.00196 |
| Sonnet 5 | $0.00000 | $0.00078 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
forms_events 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.
What it actually says
Добавление обработчиков событий на форму 1С
ВАЖНО! - при добавлении обработчика события в модуль формы, не забудь также добавить привязку события в XML-файл формы.
Файл обычно называется Form.xml и находится в родительском каталоге относительно модуля формы.
Привязки событий в XML выглядят так:
<Events>
<Event name="OnOpen">ПриОткрытии</Event>
<Event name="BeforeWrite">ПередЗаписью</Event>
<Event name="OnCreateAtServer">ПриСозданииНаСервере</Event>
</Events>
Типовые события формы:
| XML Event Name | Имя обработчика | Описание |
|---|---|---|
OnOpen |
ПриОткрытии | Клиент, при открытии формы |
OnClose |
ПриЗакрытии | Клиент, при закрытии формы |
BeforeWrite |
ПередЗаписью | Клиент, перед записью |
AfterWrite |
ПослеЗаписи | Клиент, после записи |
OnCreateAtServer |
ПриСозданииНаСервере | Сервер, создание формы |
BeforeWriteAtServer |
ПередЗаписьюНаСервере | Сервер, перед записью |
AfterWriteAtServer |
ПослеЗаписиНаСервере | Сервер, после записи |
OnReadAtServer |
ПриЧтенииНаСервере | Сервер, при чтении объекта |
Значение внутри тега <Event> - это имя процедуры-обработчика в модуле формы.
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.
- 4d ago First seen · 36 lines · 0 tokens per session scan A f2ef232b9cc0
forms_events is a cursor rule published in the GitHub repository Desko77/cursor-1c-skills (55 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 391 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.