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-eventsgit 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-events)<a href="https://agentmods.dev/skills/bxmaximum/bitrix-framework-skills/bitrix-events"><img src="https://agentmods.dev/badge/skills/bxmaximum/bitrix-framework-skills/bitrix-events/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-events"><img src="https://agentmods.dev/badge/skills/bxmaximum/bitrix-framework-skills/bitrix-events.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.00052 | $0.01274 |
| Opus 5.5 | $0.00021 | $0.00510 |
| Sonnet 5.5 | $0.00010 | $0.00255 |
| Haiku 4.5 | $0.00005 | $0.00127 |
Grade A, and why
bitrix-events 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bitrix events
Baseline: main 23.0+ · Verified: main 26.800.0
Who dispatches decides the handler signature
| Dispatcher (find it in the caller) | Examples | Handler receives | Result |
|---|---|---|---|
new Event(...) + ->send() |
own events, main:OnBeforeMailSend, ORM tablet events |
VERSION 2 (registerEventHandler, addEventHandler): the Event object. VERSION 1 (*Compatible): ...array_values($params) |
$event->getResults(); non-EventResult returns are wrapped as UNDEFINED |
GetModuleEvents() + ExecuteModuleEventEx() (legacy) |
main:OnBeforeUserAdd, OnAfterUserAdd, OnPageStart, OnEpilog, iblock:OnBeforeIBlockElementAdd |
raw args, whatever VERSION was registered — e.g. array &$arFields |
caller-specific |
- Legacy
OnBefore*: cancel =$APPLICATION->ThrowException('…'); return false;(callers check=== false). Modify data through the reference&$arFields; a returned array (['FIELDS' => …]) is ignored. - ORM tablet / highload record events use
Bitrix\Main\ORM\EventManagerandORM\EventResult::modifyFields()— seebitrix-orm; HL event names —bitrix-highloadblock.
Publish a D7 event
php bitrix.php make:event PostCreated -m vendor.blog -C Post (Since main 25.900; older: write the class) → Vendor\Blog\Public\Event\Post\PostCreatedEvent (without -C: …\Public\Event\). The generated class passes no params — add them:
namespace Vendor\Blog\Public\Event\Post;
use Bitrix\Main\Event;
final class PostCreatedEvent extends Event
{
public function __construct(public readonly int $postId, public readonly int $authorId)
{
parent::__construct('vendor.blog', 'PostCreated', ['postId' => $postId, 'authorId' => $authorId]);
}
}
$event = new PostCreatedEvent($post->getId(), $post->getAuthorId());
$event->send();
foreach ($event->getResults() as $result)
{
if ($result->getType() === \Bitrix\Main\EventResult::ERROR)
{
// caller decides: abort, log, collect errors
}
}
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 · -75 lines · -55 tokens per session 7bf4d27d1ba0
- 1mo ago First seen · 170 lines · 107 tokens per session scan A 3060daeae133
bitrix-events is a skill published in the GitHub repository bxmaximum/bitrix-framework-skills (45 stars, last pushed 8d ago), licensed MIT. It adds 52 tokens to every session and 1,274 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
roblox-lighting
Use when setting up or changing Roblox lighting, atmosphere, day/night cycles, or post-processing effects.
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…
cdd-design
Independent brainstorm orchestrator -- Node-anchored flow with digraph as single control-flow source of truth. Consumes the /superpowers:brainstorming（pi：/skill:brainstorming） flow inline as this session's baseline (one import per session), gates on mode and phase registration, runs grilling, and dispatches the…
roblox-growth-design
Use for Roblox growth: diagnosing stats, discovery, retention, onboarding, experiments, LiveOps, thumbnails, and packaging.
roblox-data
Use when writing, changing, debugging, or auditing Roblox player saves: DataStore, ProfileStore, session locks, schemas, migrations.
roblox-networking
Use when adding, changing, or auditing RemoteEvents/RemoteFunctions: argument validation, rate limits, server authority, exploit prevention.