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 agentmods add skills/shabaraba/vibing.nvim/vibing-worktree-attachnpx 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.svg" alt="Measured on agentmods" height="20"></a>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.00335 |
| Opus 5 | $0.00039 | $0.00168 |
| Sonnet 5 | $0.00015 | $0.00067 |
| Haiku 4.5 | $0.00008 | $0.00034 |
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 6d 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 steps 3-5 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.
- 6d 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 335 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
add-sponsor
Add, move or remove a sponsor logo in the README and on the install page. Use when a GitHub sponsor reaches the Team or Company tier, when a sponsorship lapses, or when a sponsor sends a new logo asset.
deep-context
Build deep codebase understanding using Capsule context, progressive-reader, and specialist agents instead of overwhelming main context. Triggers on: don't have context, understand codebase, learn about, need background. Implements progressive context building.
code-review
Pre-commit code review using code-reviewer agent for bug detection, security analysis, and quality assurance. Manual invocation only. Use before git commits to catch issues early. Blocks commits on REQUESTCHANGES verdict.
debug
Systematic debugging using error-detective and debugger agents instead of manual investigation. Triggers automatically on: error, bug, broken, failing, exception, stack trace, test failure. Orchestrates RCA-first approach with parallel agent investigation.
task-router
Decision matrix for choosing optimal approach to any task. Helps Claude decide when to delegate to sub-agents vs. working directly. Use when starting a new task or unsure of best approach.
workflow
Systematic task orchestration for complex multi-step tasks. Triggers automatically when detecting: complex task, multi-step work, coordinate, orchestrate, break down. Guides through Understand → Strategy → Plan → Execute → Verify phases for comprehensive systematic approach.