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 skills add fredrikaverpil/dotfiles --skill nvim-plugingit clone --depth 1 https://github.com/fredrikaverpil/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/fredrikaverpil/dotfiles/nvim-plugin)<a href="https://agentmods.dev/skills/fredrikaverpil/dotfiles/nvim-plugin"><img src="https://agentmods.dev/badge/skills/fredrikaverpil/dotfiles/nvim-plugin/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.
<a href="https://agentmods.dev/skills/fredrikaverpil/dotfiles/nvim-plugin"><img src="https://agentmods.dev/badge/skills/fredrikaverpil/dotfiles/nvim-plugin.svg" alt="Reviewed on agentmods" width="80" 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.00072 | $0.00344 |
| Opus 5.5 | $0.00029 | $0.00138 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 36 lines · 72 tokens per session scan A e04371f82db9
nvim-plugin is a skill published in the GitHub repository fredrikaverpil/dotfiles (260 stars, last pushed yesterday), licensed MIT. It adds 72 tokens to every session and 344 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-30.
Other skills, from other repositories
writing-skills
Use when creating new skills, editing existing skills, or verifying skills work before deployment.
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.
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available.
userscripts
Use when writing Tampermonkey/Violentmonkey/Greasemonkey userscripts, modifying website behavior or appearance, or working with .user.js files.
writing-plans
Use when you have a spec or requirements for a multi-step task, before touching code.
finishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work.