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/carlos-algms/agentic.nvim/agentic-vimdocnpx skills add carlos-algms/agentic.nvim --skill agentic-vimdocgit clone --depth 1 https://github.com/carlos-algms/agentic.nvimWhat 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.00066 | $0.00302 |
| Opus 5 | $0.00033 | $0.00151 |
| Sonnet 5 | $0.00013 | $0.00060 |
| Haiku 4.5 | $0.00007 | $0.00030 |
Grade A, and why
agentic-vimdoc 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 3d 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
Vimdoc (doc/agentic.txt)
Manually written, NOT auto-generated.
When vimdoc MUST be updated
| Source file | Vimdoc section to update |
|---|---|
lua/agentic/init.lua |
Usage (public API functions) |
lua/agentic/config_default.lua |
Configuration, Customization |
lua/agentic/theme.lua |
Customization (highlight groups) |
README.md (install/keymaps) |
Installation, Keymaps, Integrations |
Format rules
- 78-char width.
- Right-aligned tags
*agentic-section*. - Code blocks
>lua/<. - Function tags
*agentic.function_name()*. - Cross-refs
|agentic-section|. - Modeline
vim:tw=78:ts=8:ft=help:norl:.
After editing:
timeout 5 nvim --headless -c "helptags doc/" -c "quit"
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.
- 3d ago First seen · 37 lines · 66 tokens per session scan A 902ab27f1b3f
agentic-vimdoc is a skill published in the GitHub repository carlos-algms/agentic.nvim (609 stars, last pushed 10d ago), licensed MIT. It adds 66 tokens to every session and 302 once invoked, about $0.0003 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
add
Categorize new Neovim plugins and insert them into the correct markdown category files.
write-teach-commit
Draft teach: commit messages for .github/workflows/improve-add-skill.yml. Use when preparing or reviewing a correction commit that should trigger the Improve Add Skill workflow from $add categorization feedback, including moved plugin entries, removed or excluded plugins, changed .reason.md categories, or…
improve-add-skill
Improve the repo-local add skill from reviewed Neovim plugin categorization corrections. Use when a correction commit, PR review result, diff, or artifact such as a teach: commit shows that $add placed, excluded, or reasoned about plugins incorrectly and the reusable lesson should be folded back into…
git-branch-commit-pr
Automates the workflow of creating a feature branch, committing changes, and opening a PR. Use this when asked to create a branch, make changes, commit, and open a pull request for Lua code improvements or fixes.
source-drafting
Use when drafting documents, reports, posts, presentations, or review comments from source materials, or conducting research across provided documents. Enforces read-first drafting, a source map for every claim, agent verification, and separation of verified from unverified claims.
github-pr-create
Create a pull request with an auto-generated description. Use when the user asks to open a PR for the current branch's changes.