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/Diversus23/1c-feature-devWrote 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/agents/diversus23/1c-feature-dev/1c-code-explorer)<a href="https://agentmods.dev/agents/diversus23/1c-feature-dev/1c-code-explorer"><img src="https://agentmods.dev/badge/agents/diversus23/1c-feature-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.
<a href="https://agentmods.dev/agents/diversus23/1c-feature-dev/1c-code-explorer"><img src="https://agentmods.dev/badge/agents/diversus23/1c-feature-dev/1c-code-explorer.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.00060 | $0.01005 |
| Opus 5.5 | $0.00024 | $0.00402 |
| Sonnet 5.5 | $0.00012 | $0.00201 |
| Haiku 4.5 | $0.00006 | $0.00101 |
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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 · 80 lines · 60 tokens per session scan A cdfb25ee2541
1c-code-explorer is an agent published in the GitHub repository Diversus23/1c-feature-dev (13 stars, last pushed 8mo ago), with no licence file. It adds 60 tokens to every session and 1,005 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.
Other agents, from other repositories
task-verifier
Use proactively for a fresh verification pass against current code and current command results.
task-fixer
Use proactively when a fresh verifier reports gaps and a smallest safe repair is needed.
bsl-verifier
An automated verifier for BSL, the programming language used by the 1C business-software platform. It checks method signatures, shared modules, metadata objects, static-analysis diagnostics, naming rules, and allowed characters.
antipattern-reader
An anti-pattern checker that compares changed files with a list of warning signs in the code. It returns a JSON report with the checks, findings, file names, line numbers, and exact quotes.
1c-code-explorer
An analysis agent for existing 1C codebases. 1C is a business-software platform, and the agent traces how a change moves from user actions through program layers to stored data.
git-investigator
Code archaeology expert. Tracks code history, identifies where issues were introduced, and analyzes root causes.