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 dryvist/claude-code-plugins --skill troubleshoot-worktreegit clone --depth 1 https://github.com/dryvist/claude-code-pluginsWrote 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/dryvist/claude-code-plugins/troubleshoot-worktree)<a href="https://agentmods.dev/skills/dryvist/claude-code-plugins/troubleshoot-worktree"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/troubleshoot-worktree/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/dryvist/claude-code-plugins/troubleshoot-worktree"><img src="https://agentmods.dev/badge/skills/dryvist/claude-code-plugins/troubleshoot-worktree.svg" alt="Reviewed on agentmods" width="80" 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.00019 | $0.00461 |
| Opus 5.5 | $0.00008 | $0.00184 |
| Sonnet 5.5 | $0.00004 | $0.00092 |
| Haiku 4.5 | $0.00002 | $0.00046 |
Grade A, and why
troubleshoot-worktree 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 1mo 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
Git Worktree Troubleshooting
Diagnose and fix worktree, branch, and reference issues.
Quick Diagnostics
Always run first:
git worktree list
git branch -a
git status
pwd
Worktree Discovery
Never assume paths - always discover with git worktree list. The first
column is the path; the bracketed name is the branch checked out there.
Critical: Ambiguous Refname
Warning: warning: refname 'origin/main' is ambiguous
Means TWO things named origin/main:
refs/heads/origin/main- LOCAL branch (bad)refs/remotes/origin/main- remote tracking (good)
Diagnose: git show-ref origin/main
Fix: git branch -D origin/main then verify only 1 line remains with git show-ref origin/main.
The same ambiguity can occur for any branch name, not just main — on a
git-flow repo (default branch develop) watch for origin/develop too.
Substitute the branch name in the diagnose/fix commands above.
Common Errors
Branch Not Found
git fetch origin --force
git branch -a | grep -i "<branch>"
Uncommitted Changes
git add . && git commit -m "WIP" # Commit
git stash push -m "before operation" # Stash (temporary)
git checkout -- . # Discard (DESTRUCTIVE)
Embedded Git Repository
git rm --cached <folder>
echo "<folder>/" >> .gitignore
Related Skills
- troubleshoot-rebase (git-workflows) — Diagnose and recover from git rebase failures
- troubleshoot-precommit (git-workflows) — Troubleshoot pre-commit hook failures
- refresh-repo (github-workflows) — Default-branch sync
- prune-branches (github-workflows) — Worktree and branch cleanup
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.
- 1mo ago First seen · 73 lines · 19 tokens per session scan A 173fe636b7f8
troubleshoot-worktree is a skill published in the GitHub repository dryvist/claude-code-plugins (3 stars, last pushed 5d ago), licensed Apache-2.0. It adds 19 tokens to every session and 461 once invoked, about $0.0001 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-31.
Other skills, from other repositories
debug-systematic
Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
ai-diagnostic
A diagnostic framework that examines a problem across technology, processes, people, and business causes.
meta-feedback
A feedback reporter that collects bug reports and feature requests, then formats them as GitHub Issues. GitHub Issues are shared records used by development teams to track work and problems.
monitoring-observability
OpenTelemetry, structured logging, distributed tracing, alerting, and dashboards. Use when instrumenting services, designing logs/traces/metrics, defining SLOs and alerts, or debugging production behavior from telemetry.