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/project-context)<a href="https://agentmods.dev/rules/yellow-hammer/mcp-1c-platform-tools/project-context"><img src="https://agentmods.dev/badge/rules/yellow-hammer/mcp-1c-platform-tools/project-context/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/project-context"><img src="https://agentmods.dev/badge/rules/yellow-hammer/mcp-1c-platform-tools/project-context.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.00959 | $0.00959 |
| Opus 5.5 | $0.00384 | $0.00384 |
| Sonnet 5.5 | $0.00192 | $0.00192 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
project-context 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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Контекст проекта
Расширение VS Code, которое предоставляет MCP-сервер (Model Context Protocol), чтобы агенты Cursor/VS Code могли вызывать команды 1c-platform-tools по IPC. Зависит от yellow-hammer.1c-platform-tools; расширение должно быть установлено, IPC включён (1c-platform-tools.ipc.enabled).
Архитектура
- Точка входа:
src/extension.tsрегистрирует определение MCP-сервера и передаёт настройки IPC (порт, токен) через переменные окружения; процесс MCP запускает хост (Cursor/VS Code), выполняетсяout/index.js(Node). - MCP-сервер (standalone):
src/index.ts— создаёт McpServer (версия из package.json), получает список команд расширения по IPC (listCommands()), регистрирует один инструмент на команду. Транспорт: stdio. - IPC-клиент:
src/ipcClient.ts— TCP-клиент к IPC-серверу расширения (хост/порт из env или по умолчанию). Методы:listCommands(),executeCommand(commandId, args, projectPath). - Имена инструментов:
src/toolName.ts—commandIdToToolName(commandId)преобразует command ID расширения (например1c-platform-tools.configuration.loadFromSrc) в имена MCP-инструментов с сокращениями так, чтобы суммарная длина «имя сервера + имя инструмента» не превышала 60 символов (ограничение платформы). Допустимые сокращения (1Cpt, 1cpt) и правило 60 символов — в.cursor/rules/naming-abbreviations.mdc. - Логирование:
src/logger.ts— собственныйLogOutputChannelрасширения (канал «1C: Platform Tools MCP»; уровень, таймстемп и фильтрацию задаёт VS Code);src/loggerServer.ts— вывод в stderr для standalone-процесса MCP (уровень из envMCP_1C_LOG_LEVEL). - Иконка:
resources/1c-icon.png— иконка расширения, указывается в package.json.
Динамическая регистрация инструментов
Инструменты не захардкожены. При старте MCP-сервер вызывает ipcClient.listCommands(), получает список command ID от расширения (IPC-метод listCommands). Для каждого ID регистрирует server.tool(toolName, baseParamsShape, handler). Имя инструмента вычисляется из commandId через commandIdToToolName(). Добавление новой команды в 1c-platform-tools (и её отдача в listCommands) автоматически добавляет новый MCP-инструмент; в mcp-1c-platform-tools менять ничего не нужно, кроме возможного обновления сокращений в toolName.ts при превышении лимита длины.
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 · 38 lines · 959 tokens per session scan A 8fbe97c06bb1
project-context is a cursor rule published in the GitHub repository yellow-hammer/mcp-1c-platform-tools (40 stars, last pushed 4d ago), licensed MIT. It adds 959 tokens to every session, about $0.0038 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.