nvim-lua-audit

nvim-lua-audit is a skill for Claude Code from ondrasek/cc-plugins. It costs 64 tokens per session (467 once invoked), scanned A, original, Apache-2.0.

A read-only review for Neovim Lua plugins, which are extensions written in the Lua programming language. It checks the project's testing, linting, hooks, and continuous-integration setup against nine quality areas.

In plain words
What is it for?
Use it to inspect a Neovim plugin's project structure, tools, automated checks, and release-related checks, then receive a coverage report.
Why use it?
It shows what quality checks are already present and where coverage is missing before files are changed.

Skill for Claude Code

Written for Claude Code: SessionStart hook event.

Part of the blueprint plugin — 16 skills shipped together

Good fit Use it to inspect a Neovim plugin's project structure, tools, automated checks, and release-related checks, then receive a coverage report.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/ondrasek/cc-plugins/nvim-lua-audit
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 ondrasek/cc-plugins --skill nvim-lua-audit
Clone the repo
git clone --depth 1 https://github.com/ondrasek/cc-plugins

Made for: Claude Code.

Or install blueprint, the plugin that ships this one along with the rest of its 16 skills.

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 nvim-lua-audit

README.md
[![agentmods](https://agentmods.dev/badge/skills/ondrasek/cc-plugins/nvim-lua-audit/github.svg)](https://agentmods.dev/skills/ondrasek/cc-plugins/nvim-lua-audit)
Your own site
<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/nvim-lua-audit"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/nvim-lua-audit/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 nvim-lua-audit

Your own site · 80×15
<a href="https://agentmods.dev/skills/ondrasek/cc-plugins/nvim-lua-audit"><img src="https://agentmods.dev/badge/skills/ondrasek/cc-plugins/nvim-lua-audit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 64 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 467 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.
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.00064 $0.00467
Opus 5.5 $0.00026 $0.00187
Sonnet 5.5 $0.00013 $0.00093
Haiku 4.5 $0.00006 $0.00047

Measured 1mo ago against content hash 2a287d3c945c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

nvim-lua-audit 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 1mo 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.

plugins/blueprint/skills/nvim-lua-audit/SKILL.md · 48 lines

What it actually says

Neovim Lua Audit

Read-only — does not modify any files.

Context Files

Read these files before starting:

  • skills/shared/references/audit-workflow.md — the 5-step workflow structure
  • skills/nvim-lua-setup/references/methodology.md — the 9 quality dimensions (roles) to audit against
  • skills/nvim-lua-setup/references/analysis-checklist.md — what to check in the target codebase

Workflow

Follow audit-workflow.md. Neovim Lua-specific details:

1. Analyze Current State

Detect project structure (lua/, plugin/, tests/, doc/), plugin type, test framework (plenary/mini.test/busted). Inventory existing configurations in selene.toml, .stylua.toml, .luacov, .luarc.json. Check hooks, CI, installed tools.

2. Compare Against Methodology

Check each of the 9 dimensions — see methodology.md for Neovim Lua-specific tools and thresholds.

3. Check Hook Coverage

Expected hooks: SessionStart (plugin structure check), PostToolUse/Edit|Write (StyLua), Stop (quality gate), PostToolUse/Bash (semver check).

4. Check CI Coverage

Expected jobs: test (Neovim matrix), lint (selene + stylua), typecheck (optional), version.

5. Report

Present dimension/hook/CI coverage tables with recommendations. Suggest running /blueprint:nvim-lua-setup to configure missing dimensions.

Troubleshooting

No lua/ directory found: The project may not be a Neovim plugin. Suggest using the appropriate blueprint skill instead.

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. 1mo ago First seen · 48 lines · 64 tokens per session scan A 2a287d3c945c

Subscribe to this mod's changes

nvim-lua-audit is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 467 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-08-31.

Related

Other skills, from other repositories

rust-testing

Rust testing patterns including unit tests, integration tests, async testing, property-based testing, mocking, and coverage. Follows TDD methodology.

affaan-m/ECC · 31 tokens

golang-testing

Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.

affaan-m/ECC · 37 tokens

temporal-python-testing

Test Temporal workflows with pytest, time-skipping, and mocking strategies. Covers unit testing, integration testing, replay testing, and local development setup. Use when implementing Temporal workflow tests or debugging test failures.

wshobson/agents · 45 tokens

java-affected-tests

Use before opening or updating an OpenMetadata PR that changes Java, a JSON schema, an index mapping, a SQL migration, seed data or a pom — PR CI no longer runs the Java integration tests (they run only in the merge queue) and the JavaUIIT/search-it suites run only nightly, so this selects the unit tests and…

open-metadata/OpenMetadata · 120 tokens

migrate-xunit-to-xunit-v3

Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…

dotnet/skills · 149 tokens

golang-testing

Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…

samber/cc-skills-golang · 115 tokens