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-confignpx 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.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00137 | $0.02210 |
| Opus 5 | $0.00068 | $0.01105 |
| Sonnet 5 | $0.00027 | $0.00442 |
| Haiku 4.5 | $0.00014 | $0.00221 |
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 5d 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 — 173 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/nvim-fredrik/ inside the dotfiles
repo. It is symlinked into place via GNU Stow:
~/.dotfiles/nvim-fredrik/ <- actual files (edit here)
~/.dotfiles/stow/shared/.config/nvim-fredrik -> ../../../nvim-fredrik (stow entry)
~/.config/nvim-fredrik -> ~/.dotfiles/stow/shared/.config/nvim-fredrik (stow result)
Launch it with NVIM_APPNAME=nvim-fredrik nvim. Apply stow symlinks after
changes from ~/.dotfiles/stow with packages=(shared "$(uname -s)"); host="$(hostname -s)"; [ -d "$host" ] && packages+=("$host"); stow --target="$HOME" --restow --no-folding --adopt "${packages[@]}". Neovim itself
is managed by Bob, not nixpkgs -- binary at
~/.local/share/bob/nvim-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.
- 5d ago First seen · 173 lines · 137 tokens per session scan A cc8bbf59df46
nvim-config is a skill published in the GitHub repository fredrikaverpil/dotfiles (257 stars, last pushed yesterday), licensed MIT. It adds 137 tokens to every session and 2,210 once invoked, about $0.0007 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
mbo-plan
Plan a new objective end-to-end in this repo's docs/mbo Management-By-Objective system — turn a GitHub issue or a gss draft-PR worktree into consistent design/spec/plan artifacts and track it in docs/mbo/index.md. Use this whenever the user wants to START planning or designing a new feature, skill, CLI, or service…
wispr-flow-debug
Debug and test the Wispr Flow AutoHotkey dictation triggers (Copilot key + extra keys) from WSL by deploying macos.ahk to the Windows Desktop, reloading AutoHotkey, and reading the debug log. Use when an activation/trigger key isn't starting/stopping dictation, when the overlay clicks land wrong, or when verifying a…
google-docs
Integration for interacting with Google Docs and Google Workspace using the 'gws' CLI.
pr-list
List GitHub Pull Requests in a Discord-friendly format with status icons, blockquotes, and direct links. Use when the user asks for "pr list", "list PRs", "open pull requests", or a chat-ready summary of PRs for a repository.
sync-forks
Check how many of your GitHub forks are out of date and sync them.
research-evaluation
Discover and evaluate external tools/projects before adopting them, producing a consistent research dossier and (when the repo has one) a docs/mbo research design doc + tracking issue per target. Use when the user wants to "research X", "evaluate X before we adopt it", "look up X and tell me if it's useful", "start a…