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-worktree-attachgit 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-worktree-attach)<a href="https://agentmods.dev/skills/shabaraba/vibing.nvim/vibing-worktree-attach"><img src="https://agentmods.dev/badge/skills/shabaraba/vibing.nvim/vibing-worktree-attach/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/skills/shabaraba/vibing.nvim/vibing-worktree-attach"><img src="https://agentmods.dev/badge/skills/shabaraba/vibing.nvim/vibing-worktree-attach.svg" alt="Reviewed on agentmods" width="80" 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.00077 | $0.00333 |
| Opus 5.5 | $0.00031 | $0.00133 |
| Sonnet 5.5 | $0.00015 | $0.00067 |
| Haiku 4.5 | $0.00008 | $0.00033 |
Grade A, and why
vibing-worktree-attach 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 16d 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
vibing-worktree-attach
Git worktrees provide isolated working directories for parallel development. This skill points
this chat's own working_dir frontmatter at an already-existing worktree — it never creates one
(see the vibing-worktree-create skill for that) and never runs git worktree add.
Attach — "what worktrees are there? — let's go into the auth one"
Works the same whether this is a brand-new chat's first exchange or mid-conversation in an existing one.
-
Surface candidates (see the
vibing-worktree-listskill):git worktree list --porcelain -
Once the user picks one, follow step 4 of the
vibing-worktree-createskill to point this chat's ownworking_dirfrontmatter at the chosen worktree's path via thevibing-nvimMCP tools — the worktree already exists, so there's nogit worktree addstep to run first, and there's no new chat buffer to open (the current conversation continues, and its next turn already runs in the chosen worktree).
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.
- 16d ago Changed c40fbc9e9a56
- 1mo ago First seen · 28 lines · 77 tokens per session scan A 0f1105f1115b
vibing-worktree-attach is a skill published in the GitHub repository shabaraba/vibing.nvim (13 stars, last pushed today), licensed MIT. It adds 77 tokens to every session and 333 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 skills, from other repositories
nav-pilot
Dispatch a Navigator task doc to Pilot as a labeled GitHub issue. Use when user says "dispatch TASK-XX to Pilot", "hand off to Pilot", "send to Pilot", or "queue for Pilot". One-way handoff (Navigator authors the spec, Pilot executes autonomously).
dex-rollback
Rewind one receipt-backed Dex adoption through the frozen lifecycle service. Use when the user says 'undo the update', 'go back', 'that broke something after updating'. Not for applying an update; use dex-update.
pr-triage
4-phase PR backlog management with audit, deep code review, validated comments, and optional worktree setup. Use when triaging pull requests, catching up on pending code reviews, or managing a backlog of open PRs. Args: 'all' to review all, PR numbers to focus (e.g. '42 57'), 'en'/'fr' for language, no arg = audit…
security-pipeline
Use when security verification is needed - pre-commit security checks, vulnerability scanning, STRIDE threat analysis. Integrates with /handoff-verify --security and /commit-push-pr. CWE Top 25 based.
land-and-deploy
Merge PR, wait for CI, verify deploy, run canary. The complete landing pipeline.
git-ai-archaeology
Analyze AI config evolution in a git repo. Use when mapping AI adoption history, finding when configs were first introduced, charting commit velocity by month, or identifying maturity phases in a project's AI tooling.