zero-knowledge-proofs

zero-knowledge-proofs is a skill for Claude Code, Codex from LuuOW/meridian-mcp. It costs 70 tokens per session (2,158 once invoked), scanned A, original, MIT.

A guide to zero-knowledge proofs, a way to prove that a statement is true without revealing the underlying secret. It covers systems such as Groth16, PLONK, STARKs, Halo2, and tools for writing and verifying circuits.

In plain words
What is it for?
Use it to write Circom or Halo2 circuits, generate and verify proofs, build recursive proof systems, and design ZK rollups such as zkEVM-based networks.
Why use it?
It helps developers choose proof systems and understand their trade-offs when applications need privacy, compact proofs, recursion, or blockchain verification.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to write Circom or Halo2 circuits, generate and verify proofs, build recursive proof systems, and design ZK rollups such as zkEVM-based networks.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/luuow/meridian-mcp/zero-knowledge-proofs
Install

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.

Any agent
npx skills add LuuOW/meridian-mcp --skill zero-knowledge-proofs
Clone the repo
git clone --depth 1 https://github.com/LuuOW/meridian-mcp

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for zero-knowledge-proofs

README.md
[![agentmods](https://agentmods.dev/badge/skills/luuow/meridian-mcp/zero-knowledge-proofs/github.svg)](https://agentmods.dev/skills/luuow/meridian-mcp/zero-knowledge-proofs)
Your own site
<a href="https://agentmods.dev/skills/luuow/meridian-mcp/zero-knowledge-proofs"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/zero-knowledge-proofs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for zero-knowledge-proofs

Your own site · 80×15
<a href="https://agentmods.dev/skills/luuow/meridian-mcp/zero-knowledge-proofs"><img src="https://agentmods.dev/badge/skills/luuow/meridian-mcp/zero-knowledge-proofs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 70 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,158 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00070 $0.02158
Opus 5 $0.00035 $0.01079
Sonnet 5 $0.00014 $0.00432
Haiku 4.5 $0.00007 $0.00216

Measured 8d ago against content hash 84657a1baf58, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

zero-knowledge-proofs 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 8d 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.

skills/zero-knowledge-proofs/SKILL.md · 188 lines

How it starts

The opening of the file, as written. The whole thing — 188 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Zero-Knowledge Proofs

Deep authority on ZK proof system design and implementation: circuit authoring in Circom and Halo2, proof generation and on-chain verification, system tradeoffs (Groth16 vs PLONK vs STARKs), and ZK rollup architectures. Use this skill when building ZK circuits, integrating provers into applications, or reasoning about ZK-EVM equivalence levels.

Core Concepts

Proof System Tradeoffs

System Setup Proof Size Verify Time Recursive Quantum-safe
Groth16 Trusted (per-circuit) ~200 bytes ~1ms (on-chain ~200k gas) With difficulty No
PLONK Trusted (universal) ~1-2 KB ~2ms Yes (via IVC) No
STARKs Transparent ~50-200 KB ~10ms Yes Yes
Halo2 Transparent ~1-5 KB Fast Yes (accumulation) No

Groth16 dominates when proof size and on-chain verification cost are paramount and the circuit is stable (Tornado Cash, Semaphore). PLONK/UltraPLONK is preferred for systems needing a single trusted setup across many circuits. STARKs are mandatory when quantum resistance is required or a trusted setup is politically impossible (Starknet).

Circom Circuit Authoring

Circom compiles to R1CS (Rank-1 Constraint System). Every computation must be expressed as quadratic constraints a * b = c.

pragma circom 2.1.6;

include "node_modules/circomlib/circuits/poseidon.circom";
include "node_modules/circomlib/circuits/comparators.circom";

// Prove knowledge of a preimage that hashes to a public commitment
// without revealing the preimage
template PrivateSetMembership(DEPTH) {
    // Public inputs
    signal input root;
    signal input nullifierHash;
    signal input recipient;

    // Private inputs
    signal input secret;
    signal input nullifier;
    signal input pathElements[DEPTH];
    signal input pathIndices[DEPTH];

    // Recompute the leaf commitment
    component leafHasher = Poseidon(2);
    leafHasher.inputs[0] <== nullifier;
    leafHasher.inputs[1] <== secret;

    // Nullifier hash to prevent double-spend
    component nullifierHasher = Poseidon(1);
    nullifierHasher.inputs[0] <== nullifier;
    nullifierHasher.out === nullifierHash;  // constrain public output

    // Merkle path verification
    component hashers[DEPTH];
    signal levelHashes[DEPTH + 1];
    levelHashes[0] <== leafHasher.out;

    for (var i = 0; i < DEPTH; i++) {
        hashers[i] = Poseidon(2);
        // pathIndices[i] must be 0 or 1 — enforce binary
        pathIndices[i] * (1 - pathIndices[i]) === 0;

        // Left/right ordering determined by path index
        hashers[i].inputs[0] <== (1 - pathIndices[i]) * levelHashes[i] + pathIndices[i] * pathElements[i];
        hashers[i].inputs[1] <== pathIndices[i] * levelHashes[i] + (1 - pathIndices[i]) * pathElements[i];
        levelHashes[i + 1] <== hashers[i].out;
    }
    root === levelHashes[DEPTH];
}

component main {public [root, nullifierHash, recipient]} = PrivateSetMembership(20);

Read the full file on GitHub · 188 lines

Changes

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.

  1. 8d ago First seen · 188 lines · 70 tokens per session scan A 84657a1baf58

Subscribe to this mod's changes

zero-knowledge-proofs is a skill published in the GitHub repository LuuOW/meridian-mcp (0 stars, last pushed yesterday), licensed MIT. It adds 70 tokens to every session and 2,158 once invoked, about $0.0003 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-09-03.

Related

Other skills, from other repositories

zk-proofs

Zero-knowledge proofs and privacy patterns on Stellar. Covers Groth16 verification via BLS12-381 host functions (CAP-0059), Circom (on-chain verifiable today), Noir, and RISC Zero toolchains. Use when building privacy-preserving dApps, ZK verifier contracts, or wiring proving systems to Stellar.

rylsherdamz-rgb/stellar-forge · 72 tokens

starknet-js

Use when writing or debugging JavaScript/TypeScript that interacts with Starknet through the starknet.js SDK — building Call objects or calldata, encoding/decoding Cairo types (felt252, u256, structs, arrays, spans, ByteArray, Option/Result/custom enums), or working with contracts, accounts, providers, transactions…

starknet-io/starknet.js · 79 tokens

jolt

Wrap a Rust function in a Jolt zero-knowledge proof.

a16z/jolt · 15 tokens

smart-contract-reading-guide

How to read and understand smart contracts — navigating Etherscan, reading Solidity code, understanding ABIs, decoding transactions, and spotting common patterns. Use when helping users verify contracts, understand DeFi protocol mechanics, or decode on-chain activity.

nirholas/three.ws · 53 tokens

lineth-quickstart

Operating manual for the Lineth Stack quickstart — the Docker-Compose dev/demo stack at docs/getting-started/lineth-stack in the lineth-monorepo that boots a local Linea/Lineth L2 with Sepolia or local L1 finality. Use whenever you are working inside the lineth-stack quickstart and need to boot or run the stack…

LFDT-Lineth/lineth-monorepo · 228 tokens

web3-glossary

Comprehensive Web3 and DeFi glossary — definitions for 150+ terms covering blockchain, DeFi, NFTs, DAOs, L2s, and crypto culture. Use when a user asks what a term means or needs jargon explained in plain language.

nirholas/three.ws · 57 tokens