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/plugins/shabaraba/vibing.nvim/agent-plugin)<a href="https://agentmods.dev/plugins/shabaraba/vibing.nvim/agent-plugin"><img src="https://agentmods.dev/badge/plugins/shabaraba/vibing.nvim/agent-plugin/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/plugins/shabaraba/vibing.nvim/agent-plugin"><img src="https://agentmods.dev/badge/plugins/shabaraba/vibing.nvim/agent-plugin.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
vibing-nvim 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 yesterday.
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
{
"name": "vibing-nvim",
"description": "Neovim MCP tools, skills, and subagents for vibing.nvim — lets Claude Code read/edit buffers, drive LSP, and manage windows in a running Neovim instance.",
"author": {
"name": "shabaraba",
"url": "https://github.com/shabaraba"
},
"homepage": "https://github.com/shabaraba/vibing.nvim",
"repository": "https://github.com/shabaraba/vibing.nvim",
"license": "MIT",
"keywords": ["neovim", "nvim", "mcp", "lsp", "editor"],
"mcpServers": {
"vibing-nvim": {
"command": "sh",
"args": ["${CLAUDE_PLUGIN_ROOT}/mcp-server/bin/run.sh"],
"env": {
"VIBING_RPC_TIMEOUT": "30000"
}
}
}
}
What it installs
The manifest is a name and a version. 12 skills, 1 agent travel with it, and installing the plugin installs all of them — 1,071 tokens a session between them. Each is measured on its own page, and each can be installed alone.
- Skill vibing-orchestrate A 76 tokens
- Skill vibing-worker A 60 tokens
- Skill vibing-chat-search A 116 tokens
- Skill vibing-chat-recall A 130 tokens
- Skill vibing-worktree-create A 67 tokens
- Skill vibing-worktree-attach A 77 tokens
- Skill vibing-worktree-finish A 67 tokens
- Skill vibing-worktree-list A 62 tokens
- Skill nvim-context A 63 tokens
- Skill vibing-code-tour A 84 tokens
- Skill nvim-lsp-navigation A 102 tokens
- Skill vibing-worktree-run A 89 tokens
- Agent nvim-navigator A 78 tokens
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.
- yesterday First seen · 22 lines scan A 4fa2562f0f2a
vibing-nvim is a plugin published in the GitHub repository shabaraba/vibing.nvim (14 stars, last pushed today), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-10-15.
Other plugins, from other repositories
aio-golang-mastery
Write and lint idiomatic Go end-to-end — a 7-tool lint chain (build, vet, golangci-lint, govulncheck, nilaway, deadcode, race) plus reference-grade patterns for concurrency, errors, generics, gRPC, naming/style enforcement (revive 21-rule set, golangci-lint v2 production config), and production hardening.
aio-tui
Build production-grade Go TUIs on the charmbracelet v2 stack (bubbletea/v2 + lipgloss/v2) — Elm architecture, restrained styling, and elite patterns for async rendering, layout geometry, keymaps and mode machines, mouse drag and resizable panes, floating modals and command palettes, and test design with visual…
aio-watermill-kit
Build event-driven Go apps with Watermill — Router, middleware, Pub/Sub, CQRS, and integrations for Kafka, AMQP, NATS, Redis Streams, and SQL.
aio-xstate
Build XState v5 state machines the right way — design-first planning, params-first typing, and canonical actor patterns for TypeScript and React, with anti-god-machine enforcement.
laravel
Collection of skills used to work with Laravel.
functional-programming
Functional programming with Elixir, OTP patterns, Phoenix framework, and distributed systems.