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-routingnpx skills add bxmaximum/bitrix-framework-skills --skill bitrix-routinggit 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-routing)<a href="https://agentmods.dev/skills/bxmaximum/bitrix-framework-skills/bitrix-routing"><img src="https://agentmods.dev/badge/skills/bxmaximum/bitrix-framework-skills/bitrix-routing.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.00029 | $0.00345 |
| Opus 5 | $0.00015 | $0.00172 |
| Sonnet 5 | $0.00006 | $0.00069 |
| Haiku 4.5 | $0.00003 | $0.00034 |
Grade A, and why
bitrix-routing 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 3d 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.
- 3d ago First seen · 53 lines · 29 tokens per session scan A 1ea786de9ed0
bitrix-routing is a skill published in the GitHub repository bxmaximum/bitrix-framework-skills (29 stars, last pushed 8d ago), with no licence file. It adds 29 tokens to every session and 345 once invoked, about $0.0001 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
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.
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.
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.
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.