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 saajunaid/caddis-plugin --skill using-git-worktreesgit clone --depth 1 https://github.com/saajunaid/caddis-pluginWrote 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/saajunaid/caddis-plugin/using-git-worktrees)<a href="https://agentmods.dev/skills/saajunaid/caddis-plugin/using-git-worktrees"><img src="https://agentmods.dev/badge/skills/saajunaid/caddis-plugin/using-git-worktrees.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.00035 | $0.01350 |
| Opus 5 | $0.00017 | $0.00675 |
| Sonnet 5 | $0.00007 | $0.00270 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
using-git-worktrees 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 3d 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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 3d ago First seen · 218 lines · 35 tokens per session scan A 796e6376ba29
using-git-worktrees is a skill published in the GitHub repository saajunaid/caddis-plugin (0 stars, last pushed 9d ago), with no licence file. It adds 35 tokens to every session and 1,350 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
worktree-isolation
Worktree isolation for parallel agent execution in the pipeline.
git-worktrees
A guide to Git worktrees, which let you check out and work on multiple branches in separate directories at the same time. It includes patterns for isolating parallel coding-agent work.
commit
Atomic git commit with conventional message. Use when the user says "commit", "save my changes", "commit this", or wants to create a git commit. Stages specific files, writes a conventional commit message with body explaining non-obvious decisions. Never uses git add -A.
github-release-management
Comprehensive GitHub release orchestration with AI swarm coordination for automated versioning, testing, deployment, and rollback management.
lore-commit
A Git commit-writing guide that records the reasoning behind a change alongside its commit message. It defines commit types and structured notes for constraints, rejected options, confidence, risk, testing, and follow-up work.
hash-anchored-edit
A file-editing procedure that uses SHA-256 hashes to check whether a file changed before and after an edit. It also describes ownership rules for files handled by parallel agents.