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 skills add bxmaximum/bitrix-framework-skills --skill bitrix-loggergit clone --depth 1 https://github.com/bxmaximum/bitrix-framework-skillsWrote 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/skills/bxmaximum/bitrix-framework-skills/bitrix-logger)<a href="https://agentmods.dev/skills/bxmaximum/bitrix-framework-skills/bitrix-logger"><img src="https://agentmods.dev/badge/skills/bxmaximum/bitrix-framework-skills/bitrix-logger/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/skills/bxmaximum/bitrix-framework-skills/bitrix-logger"><img src="https://agentmods.dev/badge/skills/bxmaximum/bitrix-framework-skills/bitrix-logger.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.01365 |
| Opus 5.5 | $0.00024 | $0.00546 |
| Sonnet 5.5 | $0.00012 | $0.00273 |
| Haiku 4.5 | $0.00006 | $0.00136 |
Grade A, and why
bitrix-logger 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 19d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Logging (PSR-3)
Baseline: main 23.0+ · Verified: main 26.800.0
Code depends on Psr\Log\LoggerInterface; the implementation is chosen in .settings.php loggers. AddMessage2Log() — compat only.
Implementations (Bitrix\Main\Diag\)
| Class | Notes |
|---|---|
FileLogger(string $fileName, ?int $maxSize = null) |
default max 1 MB, then renamed to <file>.old; 0 = no rotation |
SysLogger(string $prefix = '', int $flags = LOG_ODELAY, int $facility = LOG_USER) |
system syslog |
EventLogger(?string $module, ?string $auditType, ?callable $callback) |
b_event_log (Event log in admin) — low volume only |
LogFormatter($showArguments = false, $argMaxChars = 30) |
default; placeholders {date} {host} {level} {delimiter} {exception} {trace} + context keys |
JsonLinesFormatter (Since main 25.300; older: LogFormatter) |
writes only $context as one JSON line — the message text is dropped, put it into context |
level and formatter settings apply only to Bitrix\Main\Diag\Logger subclasses, not to Monolog.
Get a logger
Since main 26.250* — LoggerFactory + LoggerRegistry:
use Bitrix\Main\Diag\LoggerFactory;
use Bitrix\Main\Diag\LoggerRegistry;
$logger = (new LoggerFactory())->createById('vendor.module.sync'); // NullLogger unless the id is enabled
(new LoggerRegistry())->enable('vendor.module.sync'); // option loggers:logger_is_enabled_<id> = Y
$logger = (new LoggerFactory())->createById('vendor.module.sync', [], false); // skip the registry check
- Enabled id without a
loggersentry → default logger (LOG_FILENAMEconstant) orNullLogger. - Kernel ids created this way stay silent until enabled:
main.Messenger.Receiver,main.Messenger.Requeue,main.config.feature,bizproc.imbot, … Logger::create($id, $params)— deprecated since main 26.300, the only API before 26.250; returnsnullif$idis not configured:$logger = Logger::create('id') ?? new NullLogger();.
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.
- 19d ago Changed · -127 lines · -69 tokens per session 901763c65694
- 1mo ago First seen · 235 lines · 129 tokens per session scan A 4ae52a436c3e
bitrix-logger is a skill published in the GitHub repository bxmaximum/bitrix-framework-skills (45 stars, last pushed 8d ago), licensed MIT. It adds 60 tokens to every session and 1,365 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-30.
Other skills, from other repositories
cdd-report
Analyzes the current CDD session for bugs and enhancement opportunities and files a single aggregate GitHub issue against Oscaner/skills via gh CLI. Open dedup matches become links in the issue body (never comments); closed matches are flagged as regression follow-ups, never reopened. Findings never auto-include…
roblox-performance
Use when profiling or fixing Roblox performance: low FPS, lag, memory, network load, slow phones, hot paths.
chaos-engineering
Chaos engineering: hypothesis-driven fault injection to surface weakness before users do. Use when designing a chaos experiment, planning a gameday, choosing what to inject, computing blast radius, or building a chaos maturity model.
focused-fix
This skill should be used when the user asks to "fix a bug with minimal changes", "analyze change scope for a bugfix", "find the minimal set of files to change", "do a focused bugfix", or "scope a minimal repair".
incident-commander
Production incident response. Use when handling incidents, classifying severity, reconstructing timelines, writing postmortems, generating comms templates, or building response playbooks with severity scoring and RCA frameworks.
performance-profiler
Performance profiling for Node.js, Python, and Go: CPU flamegraphs, memory leak detection, bundle analysis, query optimization, and k6 load testing. Use when diagnosing slow endpoints, memory growth, large bundles, or traffic spikes.