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.
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.
curl -O https://raw.githubusercontent.com/a16z/jolt/main/.claude/skills/update-docs/SKILL.mdgit clone --depth 1 https://github.com/a16z/joltWrote 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/a16z/jolt/update-docs)<a href="https://agentmods.dev/skills/a16z/jolt/update-docs"><img src="https://agentmods.dev/badge/skills/a16z/jolt/update-docs/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.
<a href="https://agentmods.dev/skills/a16z/jolt/update-docs"><img src="https://agentmods.dev/badge/skills/a16z/jolt/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00017 | $0.00797 |
| Opus 5.5 | $0.00007 | $0.00319 |
| Sonnet 5.5 | $0.00003 | $0.00159 |
| Haiku 4.5 | $0.00002 | $0.00080 |
Grade A, and why
update-docs 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 1mo 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are updating the Jolt documentation in book/ based on code changes since a base commit.
The base commit is: $ARGUMENTS
If no base commit was provided, ask the user for one before proceeding.
Step 1: Gather the diff
Run:
git diff $ARGUMENTS..HEAD -- '*.rs'
Also get a summary of changed files:
git diff --stat $ARGUMENTS..HEAD -- '*.rs'
Read the diff carefully. Focus on understanding:
- What functionality changed or was added
- Whether public APIs changed (new types, renamed functions, changed signatures)
- Whether new features, protocols, or subsystems were introduced
- Whether existing behavior was modified in user-visible ways
Step 2: Read the docs outline
Read book/src/SUMMARY.md to understand the current documentation structure and what topics are already covered.
Step 3: Triage — decide what needs updating
Not every code change requires a docs update. Apply this decision framework:
Changes that DO NOT need docs updates:
- Internal refactors that don't change behavior or APIs
- Performance optimizations (unless they change usage patterns or add new features like new CLI flags)
- Bug fixes (unless they change documented behavior)
- Test changes
- CI/CD changes
- Dependency bumps
- Code style / formatting changes
- Changes to internal implementation details that aren't documented
Changes that DO need docs updates:
- New user-facing features (new CLI commands, new macros, new configuration options)
- Changes to the proving/verification API that users interact with
- New architectural components that are significant enough to document
- Changes to existing documented behavior
- New optimizations or techniques that are novel and worth explaining in "How it works"
- Removed or deprecated features that are currently documented
Changes that may warrant a NEW doc page:
- A major new subsystem or feature (e.g., a new commitment scheme, a new lookup argument)
- A new user-facing workflow (e.g., a new way to profile, a new SDK feature)
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.
- 1mo ago Changed 02905c7dde9e
- 2mo ago First seen · 90 lines · 17 tokens per session scan A dd0e1b3992ee
update-docs is a skill published in the GitHub repository a16z/jolt (1,059 stars, last pushed today), licensed Apache-2.0. It adds 17 tokens to every session and 797 once invoked, about $0.0001 per session on Opus 5.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.
Other skills, from other repositories
implementing-zero-knowledge-proof-for-authentication
Zero-Knowledge Proofs (ZKPs) allow a prover to demonstrate knowledge of a secret (such as a password or private key) without revealing the secret itself. This skill implements the Schnorr identificati.
zero-knowledge-proofs
Use this skill when the user says 'ZK circuit', 'Circom', 'zk-SNARK', 'Groth16', 'PLONK', 'trusted setup', 'ptau', 'privacy-preserving proof'. Covers writing arithmetic circuits (Circom), choosing a proving system, and the trusted-setup lifecycle. Do NOT use for: full ZK domain reference (use…
zkp-toolkit
Zero-Knowledge Proof utilities - proof generation, verification, selective disclosure, ZK-Rollup batching, and benchmarking across ZK systems.
configuring-hsm-for-key-storage
Hardware Security Modules (HSMs) are tamper-resistant physical devices that safeguard cryptographic keys and perform cryptographic operations in a hardened environment. Keys stored in an HSM never lea.
implementing-aes-encryption-for-data-at-rest
AES (Advanced Encryption Standard) is a symmetric block cipher standardized by NIST (FIPS 197) used to protect classified and sensitive data. This skill covers implementing AES-256 encryption in GCM m.
configuring-certificate-authority-with-openssl
A Certificate Authority (CA) is the trust anchor in a PKI hierarchy, responsible for issuing, signing, and revoking digital certificates. This skill covers building a two-tier CA hierarchy (Root CA +.