vera-language

vera-language is a skill for Claude Code, Codex from aallan/vera. It costs 61 tokens per session (38,445 once invoked), scanned A, original, MIT.

A reference for writing Vera programs, where Vera is a statically typed functional programming language with required contracts and explicit side effects. It also explains installation, compilation, and optional language-server support.

In plain words
What is it for?
Creating or editing .vera files, checking and running programs, compiling for the browser, and using the language server.
Why use it?
It gives developers the language rules and commands needed to write valid Vera code and check it locally.

Skill for Claude CodeCodex

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

Good fit Creating or editing .vera files, checking and running programs, compiling for the browser, and using the language server.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/aallan/vera/docs
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 aallan/vera --skill docs
Clone the repo
git clone --depth 1 https://github.com/aallan/vera

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 vera-language

README.md
[![agentmods](https://agentmods.dev/badge/skills/aallan/vera/docs/github.svg)](https://agentmods.dev/skills/aallan/vera/docs)
Your own site
<a href="https://agentmods.dev/skills/aallan/vera/docs"><img src="https://agentmods.dev/badge/skills/aallan/vera/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.

agentmods 80×15 button for vera-language

Your own site · 80×15
<a href="https://agentmods.dev/skills/aallan/vera/docs"><img src="https://agentmods.dev/badge/skills/aallan/vera/docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 61 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 38,445 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.00061 $0.38445
Opus 5.5 $0.00024 $0.15378
Sonnet 5.5 $0.00012 $0.07689
Haiku 4.5 $0.00006 $0.03845

Measured today against content hash caf0d4d387c1, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vera-language 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 today.

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.

docs/SKILL.md · 2,579 lines

How it starts

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

Vera Language Reference

Vera is a programming language designed for LLMs to write. It uses typed slot references instead of variable names, requires contracts on every function, and makes all effects explicit.

Installation

Vera requires Python 3.11 or later. Node.js 22+ is optional (only needed for vera compile --target browser and browser parity tests).

Recommended — install from the GitHub source checkout. The checkout is the full environment this file teaches from: alongside the compiler and the vera CLI it carries the bundled examples/, the conformance suite in tests/conformance/ (minimal working programs, named by spec chapter and feature), and the specification in spec/:

git clone https://github.com/aallan/vera.git && cd vera
python -m venv .venv && source .venv/bin/activate   # Windows: .venv\Scripts\activate
python -m pip install -e .

For an editable source install with the language server, use python -m pip install -e ".[lsp]" — see LSP_SERVER.md. Verify the install end to end with the bundled example:

vera check examples/hello_world.vera    # prints "OK: examples/hello_world.vera"
vera run examples/hello_world.vera      # prints "Hello, World!"

Toolchain only — install the released veralang distribution from PyPI. This installs the vera command and all runtime dependencies (Lark parser, Z3 solver, wasmtime), but not the examples, conformance programs, or specification — those exist only in the checkout:

python -m venv .venv && source .venv/bin/activate   # Windows: .venv\Scripts\activate
python -m pip install veralang
vera version

For the language server on this route, install python -m pip install "veralang[lsp]".

If you are working on the compiler itself, install development dependencies too:

python -m pip install -e ".[dev]"

Platform support: README §Supported platforms lists the platforms and Python versions CI tests on, the ones that are out of scope (where install fails at dependency resolution), the workarounds, and the data behind the baseline.

For agents running in a sandbox (Claude.ai, Code Interpreter, container-based execution environments, etc.): the steps above work. Sandboxes typically have Python, git, pip, and outbound network access — that's all Vera needs. Run the install commands and verify with vera run examples/hello_world.vera before concluding that Vera "isn't available." Don't assume the sandbox lacks the toolchain — try it.

pip install vera installs a different package from PyPI (an ERAV citizen-science library — unrelated to this Vera). Use the veralang distribution or the GitHub source clone shown above; both install the vera command.

Read the full file on GitHub · 2,579 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. today Changed · +36 lines caf0d4d387c1
  2. yesterday Changed · -1 lines 950d0f3de4b9
  3. 2d ago Changed · +23 lines 1cd10c51f8ab
  4. 4d ago Changed 9450a448ef10
  5. 6d ago Changed d95059e52f86
  6. 7d ago Changed · +3 lines 4d9256d1cb20
  7. 20d ago Changed · +47 lines 9da39fbaed48
  8. 1mo ago First seen · 2,471 lines · 61 tokens per session scan A b9d5903395d5

Subscribe to this mod's changes

vera-language is a skill published in the GitHub repository aallan/vera (418 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 38,445 once invoked, about $0.0002 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.

Related

Other skills, from other repositories

kverus-run

Run the full Rust-to-Verus pipeline (migrate → spec → fix → eval → semantic audit → postprocess) in one command. Use when converting Rust code to verified Verus code end-to-end.

asterinas/KVerus · 47 tokens

kverus-semantic-audit

Compare original Rust source folders against migrated Verus code folders, identify executable-code differences that may change runtime semantics, and write per-file audit reports to an output folder. Use when checking whether Rust-to-Verus rewriting preserved executable behavior rather than merely verifying…

asterinas/KVerus · 59 tokens

kverus-migrate

Convert a Rust target into minimally modified Verus-compatible code using an explicit verification command. Use when migrating a specific file and iterating until the verification command succeeds.

asterinas/KVerus · 38 tokens

epistemic-uncertainty-quantification

Extend Sounio's epistemic types with advanced uncertainty quantification methods, such as confidence intervals, non‑Gaussian distributions, and Dempster‑Shafer evidence combination, positioning the language at the state‑of‑the‑art in measurement science.

Sounio-lang/sounio · 62 tokens

sounio-lint

Scan a .sio file for Rust-isms and suggest Sounio-native fixes.

Sounio-lang/sounio · 23 tokens

kverus-common

Shared Rust/Verus proof references for other KVerus skills. Use when Codex is repairing Verus failures, adding specifications, migrating Rust, classifying axioms or trusted boundaries, modeling external APIs, or cleaning proof scaffolding.

asterinas/KVerus · 53 tokens