Borrowing it
Nothing to install: this file belongs to laurigates/dotfiles. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/laurigates/dotfiles/main/.claude/skills/neovim-configuration/SKILL.mdgit clone --depth 1 https://github.com/laurigates/dotfilesWrote 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/laurigates/dotfiles/neovim-configuration)<a href="https://agentmods.dev/skills/laurigates/dotfiles/neovim-configuration"><img src="https://agentmods.dev/badge/skills/laurigates/dotfiles/neovim-configuration.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00089 | $0.01153 |
| Opus 5 | $0.00044 | $0.00576 |
| Sonnet 5 | $0.00018 | $0.00231 |
| Haiku 4.5 | $0.00009 | $0.00115 |
Grade A, and why
neovim-configuration 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 142 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Neovim Configuration
Expert knowledge for modern Neovim configuration with Lua scripting, plugin management, LSP setup, and AI integration for optimal development workflows.
Core Expertise
Modern Neovim Configuration
- Lua-based configuration with lazy.nvim plugin management
- LSP setup with Mason for language server management
- AI integration with claudecode.nvim and opencode.nvim
- Advanced key mapping and workflow optimization
Key Capabilities
Plugin Management & Architecture
- lazy.nvim: Modern plugin manager with lazy loading and performance optimization
- Mason.nvim: Language server, DAP server, linter, and formatter management
- Plugin Organization: Structured configuration with modular plugin setup
- Performance Optimization: Startup time optimization and lazy loading strategies
Language Server Protocol (LSP) Integration
- LSP Configuration: Multi-language LSP setup with proper keybindings
- Completion: nvim-cmp with multiple sources and intelligent completion
- Diagnostics: Error handling, linting integration, and diagnostic display
- Code Navigation: Go-to-definition, references, and symbol search
AI Integration & Automation
- claudecode.nvim: Claude Code integration for AI-powered coding in Neovim
- opencode.nvim: OpenCode AI agent integration
- Workflow Integration: AI assistance integrated into development workflows
Advanced Features
- Treesitter: Syntax highlighting, text objects, and code understanding
- Telescope: Fuzzy finder for files, buffers, grep, and more
- Git Integration: Fugitive, gitsigns, and version control workflows
- Testing Integration: neotest with multi-language testing support
- Debugging: nvim-dap with debugger integration for multiple languages
UI/UX Enhancements
- Theme Management: Color scheme selection and customization
- Status Line: Custom status line with relevant information
- File Explorer: File management with nvim-tree or oil.nvim
- Window Management: Smart window splitting and navigation
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.
- 8d ago First seen · 142 lines · 89 tokens per session scan A 7de9657e4d20
neovim-configuration is a skill published in the GitHub repository laurigates/dotfiles (10 stars, last pushed 4d ago), licensed MIT. It adds 89 tokens to every session and 1,153 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.
Other skills, from other repositories
dotfiles-bootstrap
Bootstrap a workstation with the dotfiles framework. Takes a GitHub user / owner+repo / explicit clone URL and runs dot init (which shells out to chezmoi) with the right safety prompts. Honors the active agent profile (ask / plan / apply / audit) so it defaults to dry-run in safer modes and full apply in apply.
vibe
Delegate a coding task to a cheap AI model (Mistral Vibe by default, but any provider Vibe knows about — DeepSeek, Gemini Flash, etc.) and supervise the result via git diff. Claude orchestrates, the cheap model codes. Claude consumes 500-1500 tokens per delegation regardless of how many file reads the delegate does…
work-on
End-to-end workflow for shipping a GitHub issue. Assesses complexity, builds a tailored workflow, and orchestrates skills from research through PR.
gather-context
Build comprehensive understanding of a problem by gathering context from GitHub issues, codebase exploration, git history, and linked references. Use when starting work on an issue or investigating a problem.
plan
Design an implementation as a task graph with explicit dependencies, parallel phases, and agent team topology. Use after gathering context and agreeing on an approach, when the work is large enough that sequencing it badly costs real time.
youtube
Fetch and structure the transcript from this YouTube video.