What is 1c-code-explorer?

A specialised agent for deeply investigating existing 1C code and configuration. It traces how procedures run and maps links between modules, metadata objects, and dependencies.

Use it to search code, trace function calls, inspect module structure, explore metadata dependencies, and find relevant 1C platform or configuration documentation.

It helps you understand an unfamiliar 1C system before changing it, reducing the risk of missing callers, related objects, or platform rules.

How jsfilatov/1c-full-cycle-dev configures Claude Code and Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to jsfilatov/1c-full-cycle-dev. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/jsfilatov/1c-full-cycle-dev/main/.cursor/agents/1c-code-explorer.md

Clone the repo

git clone --depth 1 https://github.com/jsfilatov/1c-full-cycle-dev

Made for: Claude Code, Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/jsfilatov/1c-full-cycle-dev/1c-code-explorer/github.svg)](https://agentmods.dev/agents/jsfilatov/1c-full-cycle-dev/1c-code-explorer)

Your own site

<a href="https://agentmods.dev/agents/jsfilatov/1c-full-cycle-dev/1c-code-explorer"><img src="https://agentmods.dev/badge/agents/jsfilatov/1c-full-cycle-dev/1c-code-explorer/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/jsfilatov/1c-full-cycle-dev/1c-code-explorer"><img src="https://agentmods.dev/badge/agents/jsfilatov/1c-full-cycle-dev/1c-code-explorer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,069 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00061	$0.01069
Opus 5.5	$0.00024	$0.00428
Sonnet 5.5	$0.00012	$0.00214
Haiku 4.5	$0.00006	$0.00107

Measured 2mo ago against content hash 019a734fae94, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

1c-code-explorer 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 2mo 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.

.cursor/agents/1c-code-explorer.md · 52 lines

How it starts

The opening of the file, as written. The whole thing — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Трассировка, шаблоны путей, MCP-FIRST, экономия чтения/вывода, TRACE, strict mode — @rules/code-explorer-rules.mdc. Имена и параметры MCP — @rules/mcp-tools.mdc; при расхождении с этим файлом или с @rules/code-explorer-rules.mdc приоритет у @rules/mcp-tools.mdc.

MCP (обязательно при доступности)

Пока в сессии есть подходящий MCP — сначала MCP; grep и широкое чтение — после (детали в @rules/code-explorer-rules.mdc). Не дублировать таблицы инструментов здесь.

Порядок исследования (трассировка, архитектура, зависимости):

codesearch
search_function — известное имя процедуры/функции
get_method_call_hierarchy — цепочки вызовов
graph_dependencies — связи объектов метаданных до выводов об архитектуре
get_module_structure — обзор модуля перед точечным Read
metadatasearch + get_metadata_details; для графа — search_metadata / business_search / answer_metadata_question (раздел Graph Metadata в @rules/mcp-tools.mdc)
docinfo (имя известно) / docsearch (имя неизвестно) — платформа
helpsearch — HTML-справка конфигурации
ssl_search — БСП / стандартные подсистемы
bsl_scope_members — API контекста (например Справочник.Имя)

Формы и разметка XML: search_metadata_forms, get_metadata_form_details, search_metadata_xml; при проверке XML — get_xsd_schema, verify_xml (разделы Metadata XML & Forms и XSD в @rules/mcp-tools.mdc).

Далее — точечное чтение по якорям MCP и шаблонам путей из @rules/code-explorer-rules.mdc.

Ход анализа

Точки входа и границы доработки → цепочка вызовов и данные (клиент/сервер, побочные эффекты) → слои и интеграции → детали платформы/БСП и производительность. Гипотезы мест и распутывание графа — § TRACE в @rules/code-explorer-rules.mdc.

Вывод

Цитаты, пути, строки, объём ответа — § TOKEN ECONOMY в @rules/code-explorer-rules.mdc. Дельта: ответ должен позволять спланировать доработку (границы, контракты, риски); явно раздели факты из кода/MCP и гипотезы; кратко отметь сильные стороны, долг и узкие места, если они следуют из цепочки.

Read the full file on GitHub · 52 lines

Changes

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.

2mo ago First seen · 52 lines · 0 tokens per session scan A 019a734fae94

Subscribe to this mod's changes

1c-code-explorer is an agent published in the GitHub repository jsfilatov/1c-full-cycle-dev (8 stars, last pushed 6mo ago), licensed MIT. It adds 61 tokens to every session and 1,069 once invoked, about $0.0002 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-31.

Debugging

1c-code-explorer next to 6 agents from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
1c-code-explorerjsfilatov/1c-full-cycle-dev	Agent	8	6mo ago	MIT	A	61	Claude Code, Cursor
review-obsidian-guidelinesuphy/obsidian-reminder	Agent	662	yesterday	MIT	A	63	Claude Code
debuggerTT-Wang/forge	Agent	35	3d ago	MIT	A	17	Claude Code
debuggerbostonaholic/rpikit	Agent	20	4d ago	MIT	A	28	Claude Code
loom-advisorcosmix/loom	Agent	65	5d ago	MIT	A	53	Claude Code
evolve-retrospectivemickeyyaya/evolve-loop	Agent	6	today	Apache-2.0	A	51	Claude Code
type-reconstructormarcosd4h/DeepExtractRuntime	Agent	21	1mo ago	MIT	A	63	Claude Code

1c-full-cycle-dev: Agent for Claude Code