jolt: Skill for Claude Code

.claude/skills/new-invariant/SKILL.md

new-invariant is a skill for Claude Code from a16z/jolt. It costs 13 tokens per session (1,380 once invoked), scanned A, original, Apache-2.0.

A Rust development workflow for adding a new invariant to jolt-eval, a tool that checks whether specified properties hold. It creates the related code, registration, and optional fuzz-testing setup.

In plain words
What is it for?
Use it to define the property being checked, its input data, and supported test targets, then add the invariant to jolt-eval. It can also create a fuzz target, which repeatedly tests varied inputs for failures.
Why use it?
It removes the repeated setup work and helps keep a new invariant consistent with existing ones. It also checks the result with linting and generated tests.

Skill for Claude Code

Written for Claude Code: argument-hint in frontmatter.

This is a16z/jolt's own configuration. It tells Claude Code how to work on jolt itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything jolt configures →

About the project

Jolt is a zero-knowledge virtual machine for RISC-V that enables programs to be executed and cryptographically proven. It is for developers and contributors working with zero-knowledge proofs and virtual machines, while the catalogue entries provide instructions and skills for using or developing Jolt.

a16z/jolt · 1,022 stars · on GitHub · jolt.a16zcrypto.com

Reuse

Borrowing it

Nothing to install: this file belongs to a16z/jolt. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/a16z/jolt/main/.claude/skills/new-invariant/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/a16z/jolt

Made for: Claude Code.

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 new-invariant

README.md
[![agentmods](https://agentmods.dev/badge/skills/a16z/jolt/new-invariant.svg)](https://agentmods.dev/skills/a16z/jolt/new-invariant)
Your own site
<a href="https://agentmods.dev/skills/a16z/jolt/new-invariant"><img src="https://agentmods.dev/badge/skills/a16z/jolt/new-invariant.svg" alt="Measured on agentmods" height="20"></a>
Per session 13 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,380 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. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
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.00013 $0.01380
Opus 5 $0.00006 $0.00690
Sonnet 5 $0.00003 $0.00276
Haiku 4.5 $0.00001 $0.00138

Measured 9d ago against content hash 472e5730b92b, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

new-invariant 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 9d 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.

.claude/skills/new-invariant/SKILL.md · 148 lines

How it starts

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

This skill handles all the boilerplate: creating the invariant struct + input type, implementing the Invariant trait, registering it in the JoltInvariants enum, creating a fuzz target (if applicable), and running sync_targets.sh.

<Execution_Policy>

  • The user must provide an invariant name (lowercase with underscores, e.g. sumcheck_binding).
  • Ask the user what property is being checked and what the input type should look like before writing code.
  • Follow existing patterns exactly — study the split_eq_bind and soundness invariants as models.
  • Always run clippy and the auto-generated tests before reporting success. </Execution_Policy>

Phase 1: Gather Requirements

  1. Validate the argument {{ARGUMENTS}}: must be a valid Rust identifier (lowercase alphanumeric + underscores). Reject otherwise.
  2. Ask the user:
    • What property does this invariant check? (becomes the description())
    • What does the input look like? (fields, types, ranges)
    • What synthesis targets should it support? (Test, Fuzz, RedTeam)
    • Does it need non-trivial setup? (e.g. preprocessing, compilation — default to Setup = ())

Phase 2: Explore Context

  1. Read jolt-eval/src/invariant/mod.rs to understand the current JoltInvariants enum and dispatch! macro.
  2. Read an existing invariant for reference:
    • Simple: jolt-eval/src/invariant/split_eq_bind.rs
    • Complex (with setup, enrich_input): jolt-eval/src/invariant/soundness.rs
  3. If the invariant tests jolt-prover-legacy functionality, explore the relevant jolt-prover-legacy modules to understand the types and APIs involved.

Phase 3: Implement

Create the invariant file at jolt-eval/src/invariant/<invariant_name>.rs with:

Input Type

#[derive(Debug, Clone, serde::Serialize, serde::Deserialize, schemars::JsonSchema)]
pub struct <Name>Input {
    // fields
}

impl<'a> Arbitrary<'a> for <Name>Input {
    fn arbitrary(u: &mut Unstructured<'a>) -> arbitrary::Result<Self> {
        // Generate random inputs with reasonable bounds
    }
}

Read the full file on GitHub · 148 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. 9d ago First seen · 148 lines · 13 tokens per session scan A 472e5730b92b

Subscribe to this mod's changes

new-invariant is a skill published in the GitHub repository a16z/jolt (1,022 stars, last pushed today), licensed Apache-2.0. It adds 13 tokens to every session and 1,380 once invoked, about $0.0001 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.