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 agents/verified-zkevm/vcvio/cryptogit clone --depth 1 https://github.com/Verified-zkEVM/VCVioWrote 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/agents/verified-zkevm/vcvio/crypto)<a href="https://agentmods.dev/agents/verified-zkevm/vcvio/crypto"><img src="https://agentmods.dev/badge/agents/verified-zkevm/vcvio/crypto.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.00000 | $0.03621 |
| Opus 5 | $0.00000 | $0.01810 |
| Sonnet 5 | $0.00000 | $0.00724 |
| Haiku 4.5 | $0.00000 | $0.00362 |
Grade A, and why
crypto 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.
How it starts
The opening of the file, as written. The whole thing — 309 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crypto Primitives and Reductions
For the LatticeCrypto/ directory layout, scheme entry points, and proof-vs-concrete split,
see docs/agents/lattice.md.
Crypto Primitive Structures
Asymmetric encryption (AsymmEncAlg)
structure AsymmEncAlg (m : Type → Type u) [Monad m] (M PK SK C : Type) where
keygen : m (PK × SK)
encrypt : (pk : PK) → (msg : M) → m C
decrypt : (sk : SK) → (c : C) → m (Option M)
Symmetric encryption (SymmEncAlg)
structure SymmEncAlg (m : Type → Type u) [Monad m] (M K C : Type) where
keygen : m K
encrypt : K → M → m C
decrypt : K → C → m (Option M)
Signatures (SignatureAlg)
structure SignatureAlg (m : Type → Type v) [Monad m] (M PK SK S : Type) where
keygen : m (PK × SK)
sign (pk : PK) (sk : SK) (msg : M) : m S
verify (pk : PK) (msg : M) (σ : S) : m Bool
For an end-to-end EUF-CMA reduction worked through the framework (Σ-protocol →
Fiat-Shamir transform → managed-RO NMA → replay forking → DLog), see
Examples/Schnorr/Signature.lean and the
Schnorr signature walkthrough.
The Schnorr-specific σ-protocol facts that feed in live in
Examples/Schnorr/SigmaProtocol.lean.
Commitment schemes (CommitmentScheme)
structure CommitmentScheme (PP M C D : Type) where
setup : ProbComp PP
commit (pp : PP) (m : M) : ProbComp (C × D)
verify (pp : PP) (m : M) (c : C) (d : D) : Bool
Defined in
VCVio/CryptoFoundations/CommitmentScheme.lean
together with PerfectlyCorrect, PerfectlyHiding, hidingExp,
bindingExp, and extractExp. The standard-model binding ≤ keyed-CR ≤ birthday bridge from a KeyedHashFamily lives in
VCVio/CryptoFoundations/HashCommitment.lean
as bindingAdvantage_toCommitment_le_keyedCRAdvantage.
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 · 309 lines · 0 tokens per session scan A 4f3828000765
crypto is an agent published in the GitHub repository Verified-zkEVM/VCVio (144 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 3,621 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-08-30.
Other agents, from other repositories
acto-critic
ACToR-style discriminator for the Thermite toolchain. Hunts for divergence between the toolchain's behavior and its authority (the design doc + the conformance corpus + Verus/Kani golden files). ALWAYS writes a FAILING test that pins down the divergence — NEVER writes a fix. Dispatch when a builder/fixer declares…
acto-builder
Multi-file authorized agent for shipping missing Thermite-toolchain infrastructure that exceeds acto-fixer's single-file scope — a whole component a design doc calls for that does not yet exist (a parser module + its AST consumers; the combinator registry + its lowering hooks; the forge check pipeline + its JSON…
acto-doc-author
Authors design docs under .design/ / .md that ADAPT to existing Thermite-toolchain code and the thermite-design.md thesis. Each REQ status table is grounded in quoted-code evidence from the current implementation. REQs are classified BINARY — SHIPPED (end-to-end functional with a non-test production consumer + tests +…
acto-fixer
Applies the MINIMAL fix for exactly ONE pinned divergence found by acto-critic. The failing test pins the divergence; the fix makes that test pass. Never bundles multiple fixes. Never refactors adjacent code. Single-file scope (escalate to acto-builder if the fix spans files). After the fix, runs the full gauntlet and…
Tenable Cloud Exposure PQC Posture Portal
Self-hosted web portal showing post-quantum cryptography readiness for cloud resources using Tenable Cloud Exposure's native SSL/TLS PQC telemetry.
speckit.checklist
Generate a custom checklist for the current feature based on user requirements.