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 skills/bxmaximum/bitrix-framework-skills/bitrix-securitynpx skills add bxmaximum/bitrix-framework-skills --skill bitrix-securitygit clone --depth 1 https://github.com/bxmaximum/bitrix-framework-skillsWhat 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.00033 | $0.00346 |
| Opus 5 | $0.00016 | $0.00173 |
| Sonnet 5 | $0.00007 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00035 |
Grade A, and why
bitrix-security 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.
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 ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 52 lines · 33 tokens per session scan A a2f0923ab6c0
bitrix-security is a skill published in the GitHub repository bxmaximum/bitrix-framework-skills (29 stars, last pushed 7d ago), with no licence file. It adds 33 tokens to every session and 346 once invoked, about $0.0002 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.
Other skills, from other repositories
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.
session-playlist
Curate playlists of Fullstory sessions for team review — bundle related sessions with notes, timestamps, and context. Use when sharing session evidence with the team, preparing for a bug review, or creating a highlight reel of user behavior.
anomaly-detector
Proactive anomaly detection — scan metrics for statistical outliers, sudden changes, and unexpected patterns. Use when the user wants to know if something unusual happened, when a metric changed unexpectedly, or for automated health monitoring.
api-monitor
Monitor API call patterns from session data — endpoint latency, error rates, popular endpoints, and API-driven UX issues. Use when investigating backend performance impact on UX, API errors affecting users, or endpoint usage patterns.
error-forensics
Investigate JavaScript errors, console errors, network failures, and crashes in production. Use when debugging user-reported issues, tracking error frequency, finding sessions with specific errors, or determining whether a bug is widespread or isolated.
experiment-analyzer
A/B test and experiment analysis — measure statistical impact, segment breakdowns, and before/after comparisons. Use when the user is running an experiment, wants to know if a variant won, or needs to measure the impact of a change.