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-configgit 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-config)<a href="https://agentmods.dev/skills/fredrikaverpil/dotfiles/nvim-config"><img src="https://agentmods.dev/badge/skills/fredrikaverpil/dotfiles/nvim-config/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-config"><img src="https://agentmods.dev/badge/skills/fredrikaverpil/dotfiles/nvim-config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 21 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 49 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00137 | $0.02111 |
| Opus 5.5 | $0.00055 | $0.00844 |
| Sonnet 5.5 | $0.00027 | $0.00422 |
| Haiku 4.5 | $0.00014 | $0.00211 |
Grade A, and why
nvim-config 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 12d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Native Neovim config
Conventions for Neovim configs built on vim.pack, lsp/ and plugin/ with no
plugin manager framework. Requires Neovim >= v0.12.0.
References — read the one the task needs:
| File | Covers |
|---|---|
references/loading-patterns.md |
vim.pack.add's load option, the three loading patterns, build hooks, profiling |
references/plugin-files.md |
File skeleton per pattern, _G.Config sharing, do/end blocks, ftplugin, option interfaces |
references/startup.md |
:h initialization step table, runtime directories, after/, exrc, help tags, standard paths |
This config's location
The native config lives at ~/.dotfiles/stow/shared/.config/nvim-fredrik/
inside the dotfiles repo. stow.sh links it into place as a whole
directory, so new files show up without a restow:
~/.dotfiles/stow/shared/.config/nvim-fredrik/ <- actual files (edit here)
~/.config/nvim-fredrik -> ~/.dotfiles/stow/shared/.config/nvim-fredrik
Launch it with NVIM_APPNAME=nvim-fredrik nvim. Neovim itself comes from
nixpkgs-unstable via home-manager (nix/shared/home/common.nix) -- binary at
~/.nix-profile/bin/nvim.
Architecture
No framework -- each directory has a single responsibility:
| Layer | Directory | Role |
|---|---|---|
| options | lua/options.lua |
All vim.opt settings, required from init.lua |
| utility | lua/ |
Shared Lua modules: lazyload.lua, merge.lua, fold.lua, toggle.lua, pickers, etc. |
| plugins | plugin/ |
Self-contained plugin files: install + setup + keymaps |
| lang plugins | plugin/lang/ |
Per-language plugin installs, custom filetypes, autocmds, and setup |
| editor settings | ftplugin/ |
Per-filetype vim.opt_local (indent, wrap, conceal) |
| server config | after/lsp/ |
All LSP server config tables (in after/ to override package defaults) |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago Changed · -1 lines bc7ff938d58b
- 17d ago Changed 9dd21b4ba780
- 28d ago Changed · -3 lines 88cabea4a969
- 1mo ago Changed c481c552b3fc
- 1mo ago First seen · 173 lines · 137 tokens per session scan A cc8bbf59df46
nvim-config is a skill published in the GitHub repository fredrikaverpil/dotfiles (259 stars, last pushed yesterday), licensed MIT. It adds 137 tokens to every session and 2,111 once invoked, about $0.0005 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.
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.
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.
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.