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/test-policy/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/test-policy)<a href="https://agentmods.dev/skills/a16z/jolt/test-policy"><img src="https://agentmods.dev/badge/skills/a16z/jolt/test-policy/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/test-policy"><img src="https://agentmods.dev/badge/skills/a16z/jolt/test-policy.svg" alt="Reviewed on agentmods" width="80" 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.00067 | $0.02291 |
| Opus 5.5 | $0.00027 | $0.00916 |
| Sonnet 5.5 | $0.00013 | $0.00458 |
| Haiku 4.5 | $0.00007 | $0.00229 |
Grade A, and why
test-policy 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 22d 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test policy
Delete tests. Touch tests and their unused support only. Never write tests or change application code; flags are separate tasks.
Posture
- Default is delete. A test survives only by matching one keep clause below. If unsure whether a clause applies, delete.
- Exception: a (b) candidate below whose bug is unconfirmed → keep and say so. False keeps are cheap; lost regressions are not.
- A surviving test carries a failure signal a maintainer wants independent of how the code is currently written.
- Keep a qualifying test whole. Never rewrite a bad test into a better one in this pass.
- Every flag names a real symbol or contract inside scope at a real
file:line. Invent nothing.
Keep list
Only these survive. Dedupe still applies, except to regressions. Tally each kept test under one primary clause.
- (a) Public contract / API behaviour (SDK, prover, and verifier entry points; the
e2e_matrixguest × mode table). - (b) Regression test pinned to a fixed bug — keep, and link the issue or commit if findable.
- (c) Invariant or algebraic property the types cannot express (sumcheck round identities, polynomial binding, field laws), asserted against independent ground truth.
- (d) Protocol / wire / format compatibility: verifier fixtures, frozen wire or transcript digests, spec vectors, golden files.
- (e) Soundness / security checks: tampered proofs, malformed inputs, and mode mismatches the verifier must reject.
For (b), find the introducing commit with git log -S '<test name or failing expression>' -- <path> and git blame <path>; add --diff-filter=A only for a new file.
A test is a (b) candidate only if that commit fixes a bug or names an issue/failing input; feature-added tests are not candidates.
Keep candidates without a confirmed bug link under (b), marked unconfirmed, with the missing evidence. Put found links in the report, not new comments.
Proptest properties and Kani proof harnesses, when present, are (c)/(e); never delete them. Keep maintained fuzz targets and their seed corpora; one-off development scaffolding is judged below. Formal checks run in CI only.
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.
- 22d ago First seen · 120 lines · 67 tokens per session scan A be53974fae61
test-policy is a skill published in the GitHub repository a16z/jolt (1,059 stars, last pushed today), licensed Apache-2.0. It adds 67 tokens to every session and 2,291 once invoked, about $0.0003 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-10-07.
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.
Strix•开放重定向
An open-redirect testing guide for checking whether a website can be tricked into sending users to an attacker-controlled address. It also covers phishing redirects, OAuth token theft, and allowlist bypasses.
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.