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 skills add shabaraba/vibing.nvim --skill vibing-orchestrategit 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/skills/shabaraba/vibing.nvim/vibing-orchestrate)<a href="https://agentmods.dev/skills/shabaraba/vibing.nvim/vibing-orchestrate"><img src="https://agentmods.dev/badge/skills/shabaraba/vibing.nvim/vibing-orchestrate.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00076 | $0.04708 |
| Opus 5 | $0.00038 | $0.02354 |
| Sonnet 5 | $0.00015 | $0.00942 |
| Haiku 4.5 | $0.00008 | $0.00471 |
Grade A, and why
vibing-orchestrate 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 today.
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 — 320 lines — stays where its author put it; the contents beside it link to each section on GitHub.
vibing-orchestrate
This chat becomes the orchestrator: it splits the work, creates one worker chat per task, sends each worker a brief, and later reports back. It does not babysit the workers — see "Hand control back" below, which is the part that most needs following.
The MCP server process is already bound to this chat's Neovim. Omit the optional legacy
rpc_port argument from every call below.
Chat or subagent?
A chat is a unit of ownership; a subagent is a unit of delegated work inside one turn. The
most expensive mistake a postmortem (#692) found was broadcasting /simplify to five worker
chats — each spawns its own subagents, so that's the chat count times the subagent count, and it
was one of two runs that hit the session limit. Decide this before creating anything.
| Subagent | Orchestrated chat | |
|---|---|---|
| Lifetime | Dies with the parent turn | Survives restarts |
| Output | One final text blob | Its own transcript |
| Visibility | None | Buffer can be opened and read, mid-task |
| Approval prompts | Can't clear one (turn just fails) | Can handle questions and approvals |
| Owns a branch/worktree | No | Yes, via working_dir frontmatter |
| Survives a rate limit | No | Yes (auto_resume / scheduled resend) |
| Spin-up cost | Low, no protocol | Floor ~61k tokens + report contract + notifications |
| Coordination can fail | No — the return value is structurally guaranteed | Yes — this run failed 9 of 18 dispatches |
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.
- today Changed · -4 lines fd2ad3f4fc1e
- yesterday Changed · +78 lines 23fc5e3299eb
- 2d ago Changed · -18 lines e478acd99595
- 3d ago Changed · +174 lines 0fe4cc1454b2
- 8d ago First seen · 90 lines · 76 tokens per session scan A 9fae03f77f26
vibing-orchestrate is a skill published in the GitHub repository shabaraba/vibing.nvim (13 stars, last pushed today), licensed MIT. It adds 76 tokens to every session and 4,708 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 skills, from other repositories
context-optimizer
Reduce Claude AI token consumption by 5x-27x using prompt-native workflows and structural code manifests. Forces Claude to reason from CONTEXTMANIFEST.md first, fetch max 3 files per turn, and output in a strict compressed format. Use when user says optimize context, reduce tokens, context optimizer, manifest, blast…
context-optimizer
Reduce Claude AI token consumption by 5x-27x using prompt-native workflows and structural code manifests. Forces Claude to reason from CONTEXTMANIFEST.md first, fetch max 3 files per turn, and output in a strict compressed format. Use when user says optimize context, reduce tokens, context optimizer, manifest, blast…
telegram-setup
Connect a Telegram bot to the Vellum Assistant gateway with automated webhook registration and credential storage.
chat-complex-documents
Chat with and search your complex documents — ask questions, extract tables and fields, and get answers grounded in the source. Connects the hosted Unstructured Transform MCP server to parse, structure, and enrich PDFs, Word/Excel/PowerPoint, images, scanned files, emails, and 60+ other formats into clean, AI-ready…
content-strategy
Develop a content strategy covering editorial positioning, content pillars, formats, calendar, governance, and topical authority planning. Use this skill whenever the user wants to plan a content program, define content pillars, build an editorial calendar, structure topic clusters, set up content governance, or align…
stakeholder-communication
Communicate effectively with stakeholders across functions and seniority levels. Use this skill when writing status updates, preparing executive reviews, sharing technical decisions with non-technical audiences, managing up, communicating bad news, or designing the communication cadence for a project. Triggers on…