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/fredrikaverpil/dotfiles/nvim-pluginnpx skills add fredrikaverpil/dotfiles --skill nvim-plugingit clone --depth 1 https://github.com/fredrikaverpil/dotfilesWhat 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.00072 | $0.00344 |
| Opus 5 | $0.00036 | $0.00172 |
| Sonnet 5 | $0.00014 | $0.00069 |
| Haiku 4.5 | $0.00007 | $0.00034 |
Grade A, and why
nvim-plugin 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
Writing Neovim plugins
:h lua-plugin (https://neovim.io/doc/user/lua-plugin/) is the authority on
layout, setup() patterns, <Plug> mappings, guard variables, health checks
and deprecation. Read it rather than working from memory — it is opinionated
and it changes. This skill only records what it leaves out.
Style
Per .stylua.toml: 2-space indentation, double quotes, 120-char width,
requires sorted by stylua.
Tooling
- vimdoc: author in Markdown, generate with
panvimdoc, then:helptags doc/. - Types: annotate the public API with LuaCATS and run
lua-typecheck-actionin CI, so luals catches breakage before users do. - Releases: SemVer via
luarocks-tag-releaseorrelease-please-action. Publish to luarocks when the plugin has Lua dependencies or is one itself.
Development loop
:restartreloads plugin changes.nvim --startuptime /tmp/nvim-startup.logto check what eager loading inplugin/costs.
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 · 36 lines · 72 tokens per session scan A e04371f82db9
nvim-plugin is a skill published in the GitHub repository fredrikaverpil/dotfiles (256 stars, last pushed 3d ago), licensed MIT. It adds 72 tokens to every session and 344 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-30.
Other skills, from other repositories
userscripts
Use when writing Tampermonkey/Violentmonkey/Greasemonkey userscripts, modifying website behavior or appearance, or working with .user.js files.
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.
subagent-driven-development
Use when executing implementation plans with independent tasks in the current Pi session using fresh subagents and review loops.
pr
Use when the user wants to create a new pull request, update an existing PR's body, open a draft PR, or preview a PR body locally before pushing.
writing-plans
Use when you have an approved design or requirements for a multi-step task, before touching code.
markdown-formatting
Format and lint markdown and MDX files using markdownlint with comprehensive rule knowledge for automated and manual fixes. Use when working with .md or .mdx files, formatting documentation, linting markdown/MDX, or when user mentions markdown issues, formatting problems, or documentation standards.