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 rules/bia-technologies/yaxunit/van-platform-detectiongit clone --depth 1 https://github.com/bia-technologies/yaxunitWhat 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.00000 | $0.00414 |
| Opus 5 | $0.00000 | $0.00207 |
| Sonnet 5 | $0.00000 | $0.00083 |
| Haiku 4.5 | $0.00000 | $0.00041 |
Grade A, and why
van-platform-detection 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- van-platform-detection — 100% identical, 0 lines differ
- van-platform-detection — 100% identical, 0 lines differ
- van-platform-detection — 100% identical, 0 lines differ
- van-platform-detection — 100% identical, 0 lines differ
What it actually says
VAN MODE: PLATFORM DETECTION
TL;DR: Detects the OS, determines path separators, and notes command adaptations required.
🌐 PLATFORM DETECTION PROCESS
graph TD
PD["Platform Detection"] --> CheckOS["Detect Operating System"]
CheckOS --> Win["Windows"]
CheckOS --> Mac["macOS"]
CheckOS --> Lin["Linux"]
Win & Mac & Lin --> Adapt["Adapt Commands<br>for Platform"]
Win --> WinPath["Path: Backslash (\\)"]
Mac --> MacPath["Path: Forward Slash (/)"]
Lin --> LinPath["Path: Forward Slash (/)"]
Win --> WinCmd["Command Adaptations:<br>dir, icacls, etc."]
Mac --> MacCmd["Command Adaptations:<br>ls, chmod, etc."]
Lin --> LinCmd["Command Adaptations:<br>ls, chmod, etc."]
WinPath & MacPath & LinPath --> PathCP["Path Separator<br>Checkpoint"]
WinCmd & MacCmd & LinCmd --> CmdCP["Command<br>Checkpoint"]
PathCP & CmdCP --> PlatformComplete["Platform Detection<br>Complete"]
style PD fill:#4da6ff,stroke:#0066cc,color:white
style PlatformComplete fill:#10b981,stroke:#059669,color:white
📋 CHECKPOINT VERIFICATION TEMPLATE (Example)
✓ SECTION CHECKPOINT: PLATFORM DETECTION
- Operating System Detected? [YES/NO]
- Path Separator Confirmed? [YES/NO]
- Command Adaptations Noted? [YES/NO]
→ If all YES: Platform Detection Complete.
→ If any NO: Resolve before proceeding.
Next Step: Load and process van-file-verification.mdc.
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 · 50 lines · 0 tokens per session scan A 1d3ddf918b3e
van-platform-detection is a cursor rule published in the GitHub repository bia-technologies/yaxunit (322 stars, last pushed 2mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 414 tokens. 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-09-01.
Other cursor rules, from other repositories
cursorrules
CLAUDE.md.
telegram-bot-tests
Test conventions for Telegram Bot library.
1c-coding-standards
Стандарты кода BSL: именование, запросы, коллекции.
1c-skd-two-pass-preprocessing
Двухпроходный СКД: предобработка детальных записей до свертки.
zpa-dependency-chain
ZPA application onboarding requires resources to be created in a specific dependency order. Skipping dependencies causes cryptic 400 errors.
evolution-no-legacy
Не плодить обратную совместимость без явного запроса.