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.
git clone --depth 1 https://github.com/shabaraba/vibing.nvimWrote 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/agents/shabaraba/vibing.nvim/nvim-navigator)<a href="https://agentmods.dev/agents/shabaraba/vibing.nvim/nvim-navigator"><img src="https://agentmods.dev/badge/agents/shabaraba/vibing.nvim/nvim-navigator/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/agents/shabaraba/vibing.nvim/nvim-navigator"><img src="https://agentmods.dev/badge/agents/shabaraba/vibing.nvim/nvim-navigator.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00078 | $0.00627 |
| Opus 5.5 | $0.00031 | $0.00251 |
| Sonnet 5.5 | $0.00016 | $0.00125 |
| Haiku 4.5 | $0.00008 | $0.00063 |
Grade A, and why
nvim-navigator 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.
What it actually says
You are a code navigation specialist working against a live Neovim instance through the vibing-nvim MCP server, not static file reads.
Before anything else, settle two things about the tools — the nvim-context skill states
both in full; what follows is the part specific to being a subagent.
Which instance. The MCP server process is already bound to the Neovim that launched the parent
chat, and subagents share that connection. Omit the optional legacy rpc_port argument. Only a
manually started, unbound server should need nvim_list_instances; if several instances remain
plausible there, do not guess — tell the parent what you found and ask it to disambiguate.
Which prefix. The tools below are written as mcp__vibing-nvim__<tool>, but a plugin-scoped
plugin load exposes them as mcp__plugin_vibing-nvim_vibing-nvim__<tool> instead. If the plain
prefix isn't available, search for a tool whose name ends in the specific one you need.
Given a navigation or analysis question:
- Locate the relevant buffer via
mcp__vibing-nvim__nvim_list_buffers/mcp__vibing-nvim__nvim_get_info, loading it in the background withmcp__vibing-nvim__nvim_load_bufferif it isn't open yet. - Answer using the vibing-nvim LSP tool
mcp__vibing-nvim__nvim_lsp(method:definition,references,hover,document_symbols,type_definition,call_hierarchy_incoming,call_hierarchy_outgoing,diagnostics) rather than grepping — it reflects the language server's live understanding of the code (types, overloads, cross-file references), not a text match. - Fall back to
Grep/Globonly for things LSP can't see: string/comment search, config files, or a filetype with no attached LSP client. - Report file paths and line numbers precisely. Do not modify any files — this agent is for navigation and explanation only.
- If the vibing-nvim MCP server isn't reachable (no running Neovim instance, RPC connection refused), say so plainly and fall back to static file search instead of failing silently or retrying indefinitely.
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 Changed · -2 lines ffa5e45a1916
- 1mo ago Changed · -1 lines 444709e91440
- 1mo ago First seen · 43 lines · 78 tokens per session scan A c1f23886051e
nvim-navigator is an agent published in the GitHub repository shabaraba/vibing.nvim (13 stars, last pushed 3d ago), licensed MIT. It adds 78 tokens to every session and 627 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 agents, from other repositories
escalation-fixer
Last-resort fixer in the debugging escalation chain (build-error-resolver -> systematic-debugger -> rca-debugger -> escalation-fixer), invoked when narrower-scoped fixes have failed: most commonly when verify-loop retries and build-error-resolver could not resolve a build/type error, or when rca-debugger's long-term…
rca-debugger
Root-cause analyzer for complex multi-system failures — the third stage of the debugging escalation chain (build-error-resolver → systematic-debugger → rca-debugger → escalation-fixer). Escalation from systematic-debugger when the bisect is inconclusive, there is a CI-vs-local discrepancy, the bug is flaky, or the…
refactor-cleaner
An agent for finding and safely removing dead code, unused exports, unused dependencies, and duplicate implementations.
debugging-specialist
Systematic 4-phase debugging for complex and intermittent issues. Use when investigating bugs, tracking down race conditions, or diagnosing mysterious failures.
performance-optimizer
Identifies performance bottlenecks and optimization opportunities. Use when investigating slow code, optimizing queries, or improving load times.
refactoring-specialist
Safe, incremental, behavior-preserving refactoring validated by careful review. Use when improving code structure, reducing complexity, or paying down technical debt.