Neva is a statically typed programming language in which programs are message-passing graphs: nodes exchange data through ports and run concurrently by default. It is for developers building compiled programs with dataflow control, visual editing, and interoperability with Go. The catalogue includes skills and instructions for working with Neva.
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/nevalang/neva/reviewnpx skills add nevalang/neva --skill reviewgit clone --depth 1 https://github.com/nevalang/nevaWrote 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/nevalang/neva/review)<a href="https://agentmods.dev/skills/nevalang/neva/review"><img src="https://agentmods.dev/badge/skills/nevalang/neva/review.svg" alt="Measured on agentmods" 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.00020 | $0.00340 |
| Opus 5 | $0.00010 | $0.00170 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
review 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 4d 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.
What it actually says
Review
Use this skill for high-signal review of a code change. The change may be a pull request, a branch, a local diff, or a patch. The goal is to publish only required changes or blocking questions.
Workflow
- Read the diff and required repository context:
AGENTS.md- canonical documentation named by its change-routing table
- Select the focused perspectives that match the change and its risk:
- correctness:
references/review-correctness.md - style and readability:
docs/user/style_guide.mdfor Neva code, plusreferences/review-readability.md - performance:
references/review-performance.md - security:
references/review-security.md
- correctness:
- Choose whether to use subagents based on the change's size and risk. For a small, focused diff, review directly; for a broad or high-risk diff, split the selected perspectives into focused passes with task-specific prompts.
- Deduplicate overlapping findings.
- Output only actionable findings and blocking questions. If there are no meaningful findings, say that clearly.
Output Contract
- Findings first, ordered by severity.
- Include file/line references whenever possible.
- Keep the output proportionate to the findings; do not impose a template when there is no meaningful feedback.
- Report clear violations of
docs/user/style_guide.mdfor Neva code. Do not report subjective style preferences.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 4d ago First seen · 38 lines · 20 tokens per session scan A 514c6bc565cc
review is a skill published in the GitHub repository nevalang/neva (1,079 stars, last pushed 13d ago), licensed MIT. It adds 20 tokens to every session and 340 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-09-01.
Other skills, from other repositories
external-model-selection
Choose optimal external AI models for code analysis, bug investigation, and architectural decisions. Use when consulting multiple LLMs via claudish, comparing model perspectives, or investigating complex Go/LSP/transpiler issues. Provides empirically validated model rankings (91/100 for MiniMax M2, 83/100 for Grok…
lsp-hover-testing
Automated LSP hover validation for Dingo transpiler. Use when testing hover functionality, validating position mappings, checking for hover drift, or debugging LSP issues after sourcemap changes.
migrate-oxlint
Guide for migrating a project from ESLint to Oxlint. Use when asked to migrate, convert, or switch a JavaScript/TypeScript project's linter from ESLint to Oxlint.
performance-lint-rules
Performance review guidance for Oxc linter rule implementations. Use only when reviewing Rust rule code under crates/oxclinter/src/rules/ or when explicitly auditing those rules for performance improvements.
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
drt-analyze
Analyze DRT cluster health for a given time range. Reconstructs the operations timeline, checks CockroachDB metrics (availability, latency, storage, changefeeds, jobs, goroutines, admission control, LSM, KV prober) and logs for anomalies, correlates findings with disruptive operations to distinguish expected…