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 skills/a16z/jolt/implement-specnpx skills add a16z/jolt --skill implement-specgit clone --depth 1 https://github.com/a16z/joltWhat 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.00017 | $0.01334 |
| Opus 5 | $0.00009 | $0.00667 |
| Sonnet 5 | $0.00003 | $0.00267 |
| Haiku 4.5 | $0.00002 | $0.00133 |
Grade A, and why
implement-spec 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 2d 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
This skill runs locally or in Claude Code cloud (claude.ai/code) — NOT in CI. It needs write access to the repo to create commits and push to the PR branch.
<Execution_Policy>
- The spec is the source of truth. Implement what it says, not more.
- Read CLAUDE.md for project conventions, testing requirements, and architecture.
- Each phase must complete before the next begins.
- Parallel execution within phases where possible.
- If something in the spec is ambiguous, post a PR comment rather than guessing.
- Do not add features, refactor code, or make improvements beyond the spec.
- If the spec lacks the
claude-spec-approvedlabel, warn that it hasn't been analyzed yet (implementation from an unanalyzed spec risks rework), but proceed if the user insists. </Execution_Policy>
Phase 1: Plan
- Read the spec: Find the
specs/*.mdfile in this PR (excludeTEMPLATE.md). If a path is provided in{{ARGUMENTS}}, use that. - Read CLAUDE.md: Understand architecture, conventions, testing requirements.
- Read
jolt-eval/README.md: Understand the eval framework — the spec's Intent → Invariants and Evaluation → Performance sections may reference it. - Explore relevant code: Use
exploreagents to understand the modules, types, and patterns the implementation will touch. - Extract evals: Scan the spec's Intent → Invariants and Evaluation → Performance sections for
jolt-evalreferences and list:- New invariants to add → each becomes a
/new-invariant <name>subtask. - New objectives to add → each becomes a
/new-objective <name>subtask. - Existing invariants/objectives that need to be changed.
- New invariants to add → each becomes a
- Create implementation plan: Based on the spec's Intent and Execution sections, determine:
- Files to create, modify, or remove
- Order of changes (dependencies first)
- How existing patterns and abstractions should be extended
- Which tasks can run in parallel vs. sequential
- Post the plan as a PR comment for visibility:
**Implementation plan for: {spec title}**
**Changes:**
1. {file/module} — {what changes and why}
2. ...
**Order:** {dependency chain}
**Parallel tasks:** {which can run simultaneously}
**Estimated scope:** {number of files, rough line count}
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.
- 2d ago First seen · 118 lines · 17 tokens per session scan A e95ae54ad63c
implement-spec is a skill published in the GitHub repository a16z/jolt (1,020 stars, last pushed 2d ago), licensed Apache-2.0. It adds 17 tokens to every session and 1,334 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.
Other skills, from other repositories
linea-dependency-maintenance
Safely plan and execute dependency maintenance for JavaScript/TypeScript (npm, pnpm) and GitHub Actions, including npm lockfiles, pnpm workspaces, catalogs, overrides, SHA-pinned action versions, release-age policies, audits, CI validation, Dependabot boundaries, PRs, and GitHub tracking issues. Use whenever the user…
pr-content-review
Review docs.linea.build content for editorial compliance (voice, terminology, naming, formatting, frontmatter) before opening or merging a pull request. Use before submitting a PR, when reviewing someone else's draft, or when asked to audit existing pages.
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…
EMILIA Trust Verification
Verify the authenticity of AI-agent authorization receipts and human-device signoffs. Use this whenever a user shares a "trust receipt", an "authorization receipt", a "signoff", or WebAuthn/passkey approval evidence and asks whether it is valid, genuine, or tampered with. Pairs with the public EMILIA Protocol MCP…
Cryptographic Analysis & Assessment
SSL/TLS auditing, cipher suite analysis, hash algorithm identification, encryption implementation review, and cryptographic weakness detection in code.
author-doc-page
Scaffold or draft a new docs.linea.build page to editorial standards. Use when creating a new page, writing a first draft, or helping a contributor who isn't a professional writer produce content that meets the documentation team's expectations.