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-landingnpx skills add bxmaximum/bitrix-framework-skills --skill bitrix-landinggit 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-landing)<a href="https://agentmods.dev/skills/bxmaximum/bitrix-framework-skills/bitrix-landing"><img src="https://agentmods.dev/badge/skills/bxmaximum/bitrix-framework-skills/bitrix-landing.svg" alt="Measured on agentmods" 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 | $0.00078 | $0.01798 |
| Opus 5 | $0.00039 | $0.00899 |
| Sonnet 5 | $0.00016 | $0.00360 |
| Haiku 4.5 | $0.00008 | $0.00180 |
Grade A, and why
bitrix-landing 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 4d 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 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.
- 4d ago First seen · 164 lines · 78 tokens per session scan A 2c6c5b3c2cc4
bitrix-landing is a skill published in the GitHub repository bxmaximum/bitrix-framework-skills (29 stars, last pushed 10d ago), with no licence file. It adds 78 tokens to every session and 1,798 once invoked, about $0.0004 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
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.
feature-adoption
Track feature adoption — who's using the new feature, how deeply, are they sticking with it, and what's blocking adoption. Use when launching a new feature, measuring feature engagement, or understanding feature usage patterns.
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.
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.".
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.
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.