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-auditnpx skills add ondrasek/cc-plugins --skill nvim-lua-auditgit 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.00064 | $0.00467 |
| Opus 5 | $0.00032 | $0.00234 |
| Sonnet 5 | $0.00013 | $0.00093 |
| Haiku 4.5 | $0.00006 | $0.00047 |
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 2d 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
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 structureskills/nvim-lua-setup/references/methodology.md— the 9 quality dimensions (roles) to audit againstskills/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.
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.
- 2d ago First seen · 48 lines · 64 tokens per session scan A 2a287d3c945c
nvim-lua-audit is a skill published in the GitHub repository ondrasek/cc-plugins (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 64 tokens to every session and 467 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.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.