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 agents/shabaraba/vibing.nvim/nvim-navigatorgit clone --depth 1 https://github.com/shabaraba/vibing.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.00078 | $0.00729 |
| Opus 5 | $0.00039 | $0.00365 |
| Sonnet 5 | $0.00016 | $0.00146 |
| Haiku 4.5 | $0.00008 | $0.00073 |
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 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
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 port. Every vibing-nvim tool takes an rpc_port naming the Neovim instance to talk to,
and you do not inherit the value the chat that spawned you was given. Take it from your task
prompt; whoever delegates to you is expected to pass it along. If it isn't there, call
nvim_list_instances once and use the port it reports — and if that lists more than one instance,
say which ones you found and ask rather than guessing.
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 tools (
mcp__vibing-nvim__nvim_lsp_definition,mcp__vibing-nvim__nvim_lsp_references,mcp__vibing-nvim__nvim_lsp_hover,mcp__vibing-nvim__nvim_lsp_document_symbols,mcp__vibing-nvim__nvim_lsp_type_definition,mcp__vibing-nvim__nvim_lsp_call_hierarchy_incoming,mcp__vibing-nvim__nvim_lsp_call_hierarchy_outgoing,mcp__vibing-nvim__nvim_diagnostics) rather than grepping — they reflect 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.
- 3d 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 729 once invoked, about $0.0004 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 agents, from other repositories
agent-developer
PROACTIVELY use this agent when developing or debugging mini-agents, understanding agent patterns, or troubleshooting MCP integrations. Read-only agent for production safety.
context-librarian
PROACTIVELY use when main Claude needs context before proceeding. Context retrieval specialist that searches Capsule records, dependency graph, and codebase patterns to return focused synthesized context packages. Use when: uncertain about context, before reading files, before spawning specialists, when user mentions…
git-workflow-manager
Use this agent for git workflow guidance, branching strategies, merge conflict resolution, and git best practices. Helps with complex git operations and maintaining clean git history.
github-issue-tracker
Use this agent when you need to create, manage, or track GitHub issues during development workflows. Creates properly formatted issues with context, labels, and assignees. Read-only agent for production safety.
refactoring-specialist
Use this agent for safe code refactoring. Specializes in improving code structure without changing behavior. Ensures refactoring is safe, incremental, and maintains all existing functionality.
code-reviewer
Use this agent for code review before commits or PRs. Checks for bugs, security issues, performance problems, and code quality. Provides actionable feedback with specific line references.