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-finishgit 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-finish)<a href="https://agentmods.dev/skills/shabaraba/vibing.nvim/vibing-worktree-finish"><img src="https://agentmods.dev/badge/skills/shabaraba/vibing.nvim/vibing-worktree-finish/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-finish"><img src="https://agentmods.dev/badge/skills/shabaraba/vibing.nvim/vibing-worktree-finish.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.00067 | $0.00301 |
| Opus 5 | $0.00034 | $0.00151 |
| Sonnet 5 | $0.00013 | $0.00060 |
| Haiku 4.5 | $0.00007 | $0.00030 |
Grade A, and why
vibing-worktree-finish 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 9d 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-finish
Git worktrees provide isolated working directories for parallel development. This skill removes
one via plain git worktree remove — no bespoke helper script, no metadata file to update beyond
this chat's own frontmatter.
Finish — "clean up this worktree"
git worktree remove <path>
Never add --force. If git refuses because of uncommitted changes, that's it protecting the
user from losing work — report the exact error and let them decide whether to commit, stash, or
discard those changes themselves, rather than retrying with --force on their behalf.
If the removed path was this chat's own working_dir, clear that frontmatter field once removal
succeeds (reverting to the main repo root) — leaving it pointed at a now-deleted directory would
break the next turn. Follow the vibing-nvim MCP buffer-editing approach described in steps 3-4
of the vibing-worktree-create skill to edit the live buffer rather than the file on disk.
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.
- 9d ago First seen · 26 lines · 67 tokens per session scan A ef0fb22f1feb
vibing-worktree-finish is a skill published in the GitHub repository shabaraba/vibing.nvim (13 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 301 once invoked, about $0.0003 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
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.
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…
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.
review-pr
Perform a comprehensive code review of a pull request.
git-worktree-clean
Clean up stale git worktrees with merged branch detection and disk usage report.