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/yellow-hammer/mcp-1c-platform-toolsWrote 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/yellow-hammer/mcp-1c-platform-tools/evolution-no-legacy)<a href="https://agentmods.dev/rules/yellow-hammer/mcp-1c-platform-tools/evolution-no-legacy"><img src="https://agentmods.dev/badge/rules/yellow-hammer/mcp-1c-platform-tools/evolution-no-legacy.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.00147 | $0.00147 |
| Opus 5 | $0.00073 | $0.00073 |
| Sonnet 5 | $0.00029 | $0.00029 |
| Haiku 4.5 | $0.00015 | $0.00015 |
Grade A, and why
evolution-no-legacy 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 7d 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
Эволюция контракта
- Не вводить обратную совместимость по собственной инициативе: чтение устаревших имён настроек, параллельные ветки в коде, алиасы, дублирующие пути чтения конфигурации.
- Пока контракт не зафиксирован для внешних потребителей — переименовываем и ломаем API прямо, правим документацию и примеры.
- Совместимость и миграции — только по явному запросу или при опубликованной версии, которую нельзя сломать без обсуждения.
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.
- 7d ago First seen · 11 lines · 147 tokens per session scan A 0ab537dc7cfe
evolution-no-legacy is a cursor rule published in the GitHub repository yellow-hammer/mcp-1c-platform-tools (37 stars, last pushed 7d ago), licensed MIT. It adds 147 tokens to every session, about $0.0007 per session on Opus 5. 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
1c-coding-standards
Coding standards for BSL, the programming language used by the 1C business software platform. They cover naming, method documentation, database queries, collections, client-server code, and performance practices.
bsl-ssl
A set of rules for developing 1C applications built on БСП, the Russian-language Standard Subsystems Library. It tells developers when to reuse library functionality, how to mark changes, and how to handle outdated objects.
1c-report-direct-query
A 1C reporting rule that runs the report query directly instead of using the standard data-composition engine (СКД). It then displays or exports the returned table manually.
1c-mdo-integrity
Rules for keeping 1C EDT MDO files structurally valid. MDO files describe configuration objects, and the rules cover unique identifiers and valid links between objects.
1c-skd-two-pass-preprocessing
A two-pass method for changing 1C report output before detailed records are combined into grouped totals. 1C's report system, СКД, builds reports by grouping and summarizing data.
1c-transactions-and-locks
Guidance for using transactions and controlled locks in 1C, where a transaction groups database changes so they can be accepted or cancelled together. It also explains the order in which locks should be taken when several operations share data.