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.
npx agentmods add instructions/keyfire/elemctl/claude-mdgit clone --depth 1 https://github.com/keyfire/elemctlWhat 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 | $0.00703 | $0.00703 |
| Opus 5 | $0.00351 | $0.00351 |
| Sonnet 5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
elemctl CLAUDE.md 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 yesterday.
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 — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Repository conventions
elemctl is a public, international project: a CLI, an MCP server and a Python library for the
1C:Enterprise.Element Console API v2. The contract the tool implements lives in
docs/SPEC.md (with a Russian twin, docs/SPEC.ru.md); this file records how the
repository itself is written.
Language of the code
- Code is English. Comments, docstrings, identifiers, test names – all of them, in
src/,tests/,tools/andeditors/. The code is read by people who do not speak Russian. - Russian stays where it faces the user: the i18n message catalog (
src/elemctl/i18n.py), argparse help strings, user-facing strings, the MCP tool descriptions and the serverINSTRUCTIONSliteral – an agent reads those in Russian. - Platform identifiers are quoted as they are:
Проект.yaml,Ресурсы,Имя,Поставщик,ВидПроекта,ОбластьВидимостиand the like are real keys and file names, not text to translate. The same goes for the Russian data of test fixtures.
Typography
Applies to English text as well:
- dashes – en dash
–(U+2013) only, never an em dash; - quotes – straight
"and', never guillemets or curly quotes; - ellipsis – three dots
..., never the…character.
Nothing internal
The repository is public. It must not carry internal project identifiers, stand names,
real application or assembly ids, internal hosts, issue keys or machine paths – not in the
code, not in comments, not in test fixtures. Neutral examples: vendors acme, globex,
applications crm-dev, demo-app.
Documentation pairs
English and Russian pages go together: README.md / README.ru.md, docs/SPEC.md /
docs/SPEC.ru.md, CHANGELOG.md / CHANGELOG.ru.md and the rest of docs/*.md. A change
to one side without the other is an unfinished change. Two pages are generated – never edit
them by hand:
docs/cli.md/docs/cli.ru.md–python scripts/gen-cli-docs.py;docs/changelog.md/docs/changelog.ru.md–node scripts/sync-docs.mjs.
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.
- yesterday First seen · 57 lines · 703 tokens per session scan A dba20c006588
elemctl CLAUDE.md is an instructions file published in the GitHub repository keyfire/elemctl (4 stars, last pushed 2d ago), licensed MIT. It adds 703 tokens to every session, about $0.0035 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-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
buildNext
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
langchain AGENTS.md
Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.