Ae4
- Category
- analysis-evasion
- Confidence
- 80% confidence
- Finding
Suspicious Unicode normalization or mixed-script content
- Content
Security audit
Security checks for vulnerabilities and agentic risk
This skill is a coherent guide for installing and using a formal proof CLI, with expected but real costs and supply-chain considerations.
Install only if you are comfortable running a research CLI from GitHub, using Lean, and potentially sending theorem prompts to an LLM provider. Pin the documented version, prefer a clean project environment, protect API keys, and start with low samples, rounds, and timeouts before larger proof searches.
Suspicious Unicode normalization or mixed-script content
Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
## Pitfalls
1. **Prose statements do not work** — `prove` expects a Lean header (`theorem … := by`).
2. **No Lean ⇒ no verification** — generation may still run, but nothing is compiler-checked;
check `omega status` and `lean --version` before interpreting results.
3. **Unbounded sampling is the usual budget blow-up.**
4. **`import Mathlib` is the default import set** — a narrower set compiles much faster; use
The skill requests shell, file read/write, and network access, which together enable package installation, downloading code from GitHub, modifying local configuration, and invoking external tools. While these permissions are functionally aligned with installing and running a CLI, they create a meaningful attack surface if the referenced package, wheel, or remote backend is compromised or if a user runs the commands in a sensitive environment.
tags: [lean4, theorem-proving, formal-verification, proof-search, mcts]
author: Li Shen
version: 1.0.3
permissions: [shell, file_read, file_write, network]
metadata:
hermes:
homepage: https://github.com/diamond2nv/omega-architect