What is nvim-lua-setup?

A setup guide for Neovim Lua plugins. Neovim is a text editor that can be extended with Lua code; the guide applies checks for code quality, tests, hooks, and continuous integration.

Use it when configuring linting, formatting, tests, local hooks, tool settings, or a CI pipeline for a Neovim plugin.

It gives a Lua plugin a consistent way to find mistakes and check changes automatically. It also accounts for the Lua version used inside Neovim.

nvim-lua-setup — Skill by ondrasek

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.

agentmods

npx agentmods add skills/ondrasek/cc-plugins/nvim-lua-setup

Any agent

npx skills add ondrasek/cc-plugins --skill nvim-lua-setup

Clone the repo

git clone --depth 1 https://github.com/ondrasek/cc-plugins

Made for: Claude Code, Codex.

Per session 74 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 813 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00074	$0.00813
Opus 5	$0.00037	$0.00407
Sonnet 5	$0.00015	$0.00163
Haiku 4.5	$0.00007	$0.00081

Measured yesterday against content hash f77a6789f288, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

nvim-lua-setup 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 yesterday.

The scan reads SKILL.md. This mod also ships 5 executable files (templates/auto-commit.sh, templates/per-edit-fix.sh, templates/quality-gate.sh, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

plugins/blueprint/skills/nvim-lua-setup/SKILL.md · 73 lines

How it starts

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

Neovim Lua Setup

Critical Rules

Always present analysis and plan to the user before making changes
Merge, don't replace — preserve existing selene.toml, .stylua.toml, CI jobs, hooks
Always configure for LuaJIT/Lua 5.1 (Neovim's embedded Lua)
All hook scripts must be executable (chmod +x)

Context Files

Read these files before starting:

skills/shared/references/methodology-framework.md — shared principles, hook architecture, exit codes, settings.json format
skills/shared/references/setup-workflow.md — the 6-phase workflow structure
skills/nvim-lua-setup/references/methodology.md — Neovim Lua-specific 9 dimensions, thresholds, tool research guidance
skills/nvim-lua-setup/references/analysis-checklist.md — what to check in the target codebase
skills/nvim-lua-setup/templates/ — annotated examples showing structural patterns. Use templates for patterns but substitute the tools chosen during research.

Workflow

Follow the 6-phase workflow from setup-workflow.md.

Phase 1: Analyze

Follow analysis-checklist.md systematically: project structure (lua/, plugin/, tests/, doc/), plugin type, test framework (plenary/mini.test/busted), existing tools, CI, maturity.

Phase 2: Plan

Research tools for each of the 9 dimensions. Neovim Lua-specific files to plan:

selene.toml + vim.toml — Selene linter configuration with Neovim globals
.stylua.toml — StyLua formatter configuration
.luacov — coverage configuration
.luarc.json — lua-language-server configuration
.claude/hooks/ — quality-gate.sh, per-edit-fix.sh, session-start.sh, optionally auto-commit.sh
.claude/settings.json — hook registrations (see methodology-framework.md for format)
.github/workflows/ci.yml — CI pipeline with Neovim version matrix
Makefile — development commands
CLAUDE.md — project instructions
semver-check.sh — only when Dimension 9 is activated at level 3

Present complete plan and wait for approval.

Read the full file on GitHub · 73 lines

Files

What ships with it

16 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.

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.

yesterday First seen · 73 lines · 74 tokens per session scan A f77a6789f288

Subscribe to this mod's changes

nvim-lua-setup is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 74 tokens to every session and 813 once invoked, about $0.0004 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-31.

Code review DevOps and cloud Testing

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

babysit-pr

Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…

openai/codex · 114 tokens

imagegen

Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…

openai/codex · 113 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens