bitrix-settings

A guide to Bitrix kernel settings stored in .settings.php and .settingsextra.php, covering connections, caching, sessions, security, routing, messaging, email, and logging.

In plain words
What is it for?
Use it when configuring database connections, cache, sessions, error handling, routes, SMTP, loggers, or related kernel services.
Why use it?
It makes changes to core application behaviour easier to locate and control, including read-only settings.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/bxmaximum/bitrix-framework-skills/bitrix-settings
Any agent
npx skills add bxmaximum/bitrix-framework-skills --skill bitrix-settings
Clone the repo
git clone --depth 1 https://github.com/bxmaximum/bitrix-framework-skills

Made for: Claude Code, Codex.

Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,263 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.

ModelPer sessionOnce invoked
Fable 5 $0.00070 $0.02263
Opus 5 $0.00035 $0.01131
Sonnet 5 $0.00014 $0.00453
Haiku 4.5 $0.00007 $0.00226

Measured 2d ago against content hash a0a8e1b37d4a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

bitrix-settings 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 2d 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.

skills/bitrix-settings/SKILL.md · 206 lines

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.

Read it on GitHub

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.

  1. 2d ago First seen · 206 lines · 70 tokens per session scan A a0a8e1b37d4a

Subscribe to this mod's changes

bitrix-settings is a skill published in the GitHub repository bxmaximum/bitrix-framework-skills (29 stars, last pushed 7d ago), with no licence file. It adds 70 tokens to every session and 2,263 once invoked, about $0.0003 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-30.

Related

Other skills, from other repositories

form-analyzer

Form field-level analysis — abandonment by field, validation errors, time-to-complete, and which fields cause users to leave. Use when investigating form performance, signup drop-off, or checkout form friction.

reatlat/fullstory-claude-plugin · 44 tokens

funnel-doctor

Conversion funnel analysis — find where users drop off, quantify the loss, and diagnose why. Use when asking about conversion rates, funnel abandonment, checkout completion, signup flow performance, or "where are we losing users.".

reatlat/fullstory-claude-plugin · 48 tokens

lifecycle-analyzer

Analyze the user lifecycle — new, active, at-risk, and churned users. Use when understanding user progression, identifying at-risk users, or measuring lifecycle conversion rates.

reatlat/fullstory-claude-plugin · 39 tokens

persona-builder

Build behavioral user personas from session data — identify distinct user types by their actual behavior, not demographics. Use when the team needs data-driven personas, wants to understand who their users really are, or needs to align product decisions to real user behavior.

reatlat/fullstory-claude-plugin · 52 tokens

privacy-auditor

Audit Fullstory session capture for PII leaks, verify privacy rules, and check recording block rules. Use when the user is concerned about privacy compliance, wants to verify masking rules, or needs to find sessions that may contain sensitive data.

reatlat/fullstory-claude-plugin · 52 tokens

scroll-depth-analyzer

Analyze how far users scroll on key pages — content visibility, where users stop reading, and whether important content is being seen. Use when evaluating page layout, content effectiveness, or CTA placement.

reatlat/fullstory-claude-plugin · 43 tokens