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/frigatecaptain/elucidatingyourllm/pre-install-checkgit clone --depth 1 https://github.com/FrigateCaptain/ElucidatingYourLLMWrote 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/rules/frigatecaptain/elucidatingyourllm/pre-install-check)<a href="https://agentmods.dev/rules/frigatecaptain/elucidatingyourllm/pre-install-check"><img src="https://agentmods.dev/badge/rules/frigatecaptain/elucidatingyourllm/pre-install-check.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.00358 | $0.00358 |
| Opus 5 | $0.00179 | $0.00179 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
Grade A, and why
pre-install-check 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.
What it actually says
Pre-Installation Compatibility Check [MANDATORY]
Before installing any application or package — verify compatibility with the target system.
When installing new software (via a package manager, downloading binaries, snap, flatpak, or manual installation):
-
Determine application requirements:
- Minimum OS version
- Required libraries and their versions (GLIBC, libstdc++, etc.)
- CPU architecture (x86_64, ARM, etc.)
- Dependencies (runtime, frameworks)
-
Determine target system parameters:
- OS version:
lsb_release -aorcat /etc/os-release - GLIBC version:
ldd --version | head -1 - Architecture:
uname -m - Other dependencies as needed
- OS version:
-
Compare and decide:
- If requirements are compatible → proceed with installation
- If incompatible → stop, inform the user of the conflict, and suggest alternatives:
- An older / compatible application version
- Installation via a container (Docker, Flatpak, AppImage)
- System upgrade (if acceptable)
-
Sources for requirement information:
- Application release page (GitHub Releases, changelog)
- Official documentation
- If no explicit information — search the web:
"[app name] [version] system requirements linux"
Reason: Installing incompatible software causes errors (e.g. GLIBC_2.36 not found), wastes time on diagnosis, and may require removal.
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 · 37 lines · 358 tokens per session scan A c52033d10f80
pre-install-check is a cursor rule published in the GitHub repository FrigateCaptain/ElucidatingYourLLM (14 stars, last pushed today), licensed MIT. It adds 358 tokens to every session, about $0.0018 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 cursor rules, from other repositories
kotlin-springboot-rules
Cursor rule "kotlin-springboot-rules" from holtwood/awesome-cursorrules-zh, covering 项目结构与组织, 编码风格与约定, 地道的 kotlin 用法 and 实现模式与设计.
springboot-jpa-best-practices
Java Spring Boot + JPA 项目最佳实践，涵盖分层架构、注解、事务、异常处理、安全与代码风格等。.
nestjs-general-guidelines
在 'src' 目录中指定 NestJS 特定的架构原则、模块化设计和测试实践。.
protocol-buffer-definitions-rule
在项目中处理 Protocol Buffer 定义文件的规则。.
nestjs-core-module-guidelines
为 NestJS 中的核心模块强制执行特定指导原则，专注于全局过滤器、中间件、守卫和拦截器。.
laravel-package-coding-standards
Cursor AI 编程规则精选集 | 132+ 规则，覆盖前端/后端/AI/DevOps 等 32 个领域.