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/code-style)<a href="https://agentmods.dev/rules/yellow-hammer/mcp-1c-platform-tools/code-style"><img src="https://agentmods.dev/badge/rules/yellow-hammer/mcp-1c-platform-tools/code-style/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/yellow-hammer/mcp-1c-platform-tools/code-style"><img src="https://agentmods.dev/badge/rules/yellow-hammer/mcp-1c-platform-tools/code-style.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.00307 | $0.00307 |
| Opus 5.5 | $0.00123 | $0.00123 |
| Sonnet 5.5 | $0.00061 | $0.00061 |
| Haiku 4.5 | $0.00031 | $0.00031 |
Grade A, and why
code-style 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 1mo 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
Стиль кода и коммиты
Коммиты
- Conventional Commits: префиксы
feat:,fix:,docs:,chore:,refactor:и т.д. - Сообщения коммитов — на русском.
Язык в коде и интерфейсе
- Комментарии в коде: на русском.
- Сообщения пользователю (showInformationMessage, showErrorMessage, текст в UI): на русском.
- Строки для логов: на русском.
TypeScript
- Строгий режим (tsconfig), импорты Node с префиксом
node:где уместно. - Избегать
any; использовать типы из@types/vscode,@types/node.
JSDoc
- Документировать экспортируемые сущности и модули; комментарии на русском.
- Подробные правила — в jsdoc.mdc.
Перед коммитом
- Удалять отладочный вывод и лишние комментарии.
Эволюция: .cursor/rules/evolution-no-legacy.mdc.
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.
- 1mo ago First seen · 35 lines · 307 tokens per session scan A 26c1fe0c2460
code-style is a cursor rule published in the GitHub repository yellow-hammer/mcp-1c-platform-tools (41 stars, last pushed 5d ago), licensed MIT. It adds 307 tokens to every session, about $0.0012 per session on Opus 5.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.
code-review-checklist
A code-review checklist for 1C source files, including BSL and OS files. It groups findings by severity and checks issues such as security, performance, errors, access control, duplication, and maintainability.
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.
bsp-profile-rights-api
Rules for creating and updating access-group profiles in БСП 3.x, the Standard Subsystems Library used by several 1C business applications. They explain how roles, permissions, users, and row-level access restrictions are represented in code.
edt-form-xml-requirements
A set of rules for XML form files used by EDT, a development environment for 1C business applications. It describes form details that the code generator does not add automatically.
sdd-workflow
A nine-phase Specification-Driven Development workflow for planning complex 1C software changes before writing code. 1C is a business software platform commonly used for accounting and enterprise operations.