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/joelreymont/pz/leannpx skills add joelreymont/pz --skill leangit clone --depth 1 https://github.com/joelreymont/pzWrote 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/joelreymont/pz/lean)<a href="https://agentmods.dev/skills/joelreymont/pz/lean"><img src="https://agentmods.dev/badge/skills/joelreymont/pz/lean.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.1 | $0.00032 | $0.00598 |
| Opus 5 | $0.00016 | $0.00299 |
| Sonnet 5 | $0.00006 | $0.00120 |
| Haiku 4.5 | $0.00003 | $0.00060 |
Grade C, and why
lean scanned grade C with 1 finding 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
If `.lake/` is corrupt: `rm -rf .lake && lake update && lake build`. How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lean 4 Proofs
Build and type-check the formal verification proofs in lean/.
Toolchain
- elan:
~/.elan/bin/ - lean/lake/leanc: all via elan
- Project:
lean/in pz root, initialized withlake init pz-proofs math
Build
cd lean && ~/.elan/bin/lake build
First build downloads mathlib (~10 min). Subsequent builds are incremental (~seconds).
If .lake/ is corrupt: rm -rf .lake && lake update && lake build.
After adding a dependency to lakefile.toml: lake update before lake build.
Project Structure
lean/
lakefile.toml # project config, mathlib dependency
lean-toolchain # pinned lean version
PzProofs.lean # root module (imports all proof files)
PzProofs/
Basic.lean # auto-generated stub
Mask.lean # Proof 1: tool mask sanitization
Approval.lean # Proof 4: approval flow (future)
Policy.lean # Proof 2: signed policy (future)
Ownership.lean # Proof 3: file ownership (future)
Crypto.lean # abstract signature scheme (future)
Adding a Proof
- Create
lean/PzProofs/Name.lean - Add
import PzProofs.Nametolean/PzProofs.lean cd lean && ~/.elan/bin/lake build- If it type-checks, the proof is valid
Key Tactics
bv_decide: automatic bitvector reasoning via SAT. Handles all mask proofs.omega: linear arithmetic over naturals/integerssimp: simplification with lemma databaseintro/exact/have: manual proof stepsby decide: decidable propositions (finite enums, bool)
BitVec for Mask Proofs
Zig u16 maps to Lean BitVec 16. Operations:
&&&= bitwise AND,|||= bitwise OR,~~~= complement<<<= shift left,≤= unsigned less-or-equal.getLsbD i= get bit at position i
bv_decide solves all fixed-width bitvector properties exhaustively.
Proof Plan
See docs/LEAN-PROOF.md for the full verification plan with 4 proofs, acceptance criteria, and dependencies.
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.
- 5d ago First seen · 71 lines · 32 tokens per session scan C a4b70ebe1f72
lean is a skill published in the GitHub repository joelreymont/pz (95 stars, last pushed 5mo ago), licensed MIT. It adds 32 tokens to every session and 598 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
instrument-data-to-allotrope
Convert laboratory instrument output files (PDF, CSV, Excel, TXT) to Allotrope Simple Model (ASM) JSON format or flattened 2D CSV. Use this skill when scientists need to standardize instrument data for LIMS systems, data lakes, or downstream analysis. Supports auto-detection of instrument types. Outputs include full…
exploratory-data-analysis
Perform bounded, local exploratory analysis of explicitly supported scientific files. Use for redacted CSV/TSV/JSON profiles; optional NumPy, HDF5, FASTA/FASTQ, and basic image metadata inspection; missingness/leakage audits; outlier and transformation sensitivity; and rigorous EDA report scaffolds. Other domain…
matlab
Build, review, migrate, and safely plan MATLAB or GNU Octave numerical workflows, including arrays, tabular/time data, tests, projects, graphics, MAT files, and explicit Python interoperability.
phylogenetics
Build and analyze phylogenetic trees using MAFFT (multiple alignment), IQ-TREE 2 (maximum likelihood), and FastTree (fast NJ/ML). Visualize with ETE3 or FigTree. For evolutionary analysis, microbial genomics, viral phylodynamics, protein family analysis, and molecular clock studies.
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
mapping-to-snomed
Maps clinical concept spans extracted by OpenMed to SNOMED CT concepts through a USER-SUPPLIED terminology server (the user's own Ontoserver, Snowstorm, or UMLS/UTS), never a bundled vocabulary. Use when the user wants to code findings, disorders, procedures, body structures, or substances to SNOMED CT, run an ECL…