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/ondrasek/cc-plugins/nvim-lua-explainnpx skills add ondrasek/cc-plugins --skill nvim-lua-explaingit clone --depth 1 https://github.com/ondrasek/cc-pluginsWhat 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.00069 | $0.00460 |
| Opus 5 | $0.00034 | $0.00230 |
| Sonnet 5 | $0.00014 | $0.00092 |
| Haiku 4.5 | $0.00007 | $0.00046 |
Grade A, and why
nvim-lua-explain 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.
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
Neovim Lua Explain
Read-only — does not modify any files.
Context Files
skills/shared/references/explain-pattern.md— shared answer format and behaviorskills/shared/references/methodology-framework.md— shared principles, hook architectureskills/nvim-lua-setup/references/methodology.md— Neovim Lua-specific dimensions, rationale, adaptation rulesskills/nvim-lua-setup/references/analysis-checklist.md— how projects are analyzed
Example Questions
"Why selene instead of luacheck?" → Dimension 2. Selene is actively maintained, supports custom std libraries for Neovim globals, better error messages, community standard.
"What's the coverage threshold?" → Dimension 1. 75% default; 50% new; 80% library. Lua coverage tooling (luacov) is less mature.
"Why StyLua for formatting?" → Dimension 2. Fast (written in Rust), opinionated, supports LuaJIT syntax, widely adopted in Neovim ecosystem.
"Why is security analysis limited?" → Dimension 4. No Lua equivalent of bandit/cargo-audit. Uses selene rules + grep patterns.
"How does testing work with Neovim?" → Dimension 1. Test framework detection (plenary, mini.test, busted), headless Neovim execution, minimal_init.lua.
"Why LuaJIT and not Lua 5.4?" → Neovim Lua-Specific Patterns. Neovim embeds LuaJIT (Lua 5.1). All tools must target LuaJIT.
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 · 33 lines · 69 tokens per session scan A c6eeb045f0bc
nvim-lua-explain is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 69 tokens to every session and 460 once invoked, about $0.0003 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…
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…
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…