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-listgit 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-list)<a href="https://agentmods.dev/skills/shabaraba/vibing.nvim/vibing-worktree-list"><img src="https://agentmods.dev/badge/skills/shabaraba/vibing.nvim/vibing-worktree-list.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.00062 | $0.00339 |
| Opus 5 | $0.00031 | $0.00169 |
| Sonnet 5 | $0.00012 | $0.00068 |
| Haiku 4.5 | $0.00006 | $0.00034 |
Grade A, and why
vibing-worktree-list 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 8d 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-list
Git worktrees provide isolated working directories for parallel development. This skill uses
plain git commands — no bespoke helper script, no metadata file. A worktree's existence on disk
is its entire state.
Directory convention
Worktrees created for isolated work go under .vibing/worktrees/<branch-name>/ at the git
root — flat, one worktree per directory, nothing else stored alongside it. This convention is
also stated in every vibing.nvim chat's system prompt.
List — "what worktrees exist?"
git worktree list --porcelain
For a one-line hint of what was last done on a given worktree's branch:
git log -1 --format=%s <branch>
This shows every worktree registered against the repo, not just ones under
.vibing/worktrees/ — including ones created outside vibing.nvim entirely (a bare
git worktree add, or claude --worktree run directly in a terminal). Present branch, path,
and (if you fetched it) the last commit message so the user can pick one, whether they're asking
out of curiosity or as a lead-in to attaching (see the vibing-worktree-attach skill).
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.
- 8d ago First seen · 35 lines · 62 tokens per session scan A 8e1cb24f9073
vibing-worktree-list is a skill published in the GitHub repository shabaraba/vibing.nvim (13 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 339 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.