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 mzored/superpowers-cc-to-codex --skill using-git-worktrees-codexgit clone --depth 1 https://github.com/mzored/superpowers-cc-to-codexWrote 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/mzored/superpowers-cc-to-codex/using-git-worktrees-codex)<a href="https://agentmods.dev/skills/mzored/superpowers-cc-to-codex/using-git-worktrees-codex"><img src="https://agentmods.dev/badge/skills/mzored/superpowers-cc-to-codex/using-git-worktrees-codex/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/mzored/superpowers-cc-to-codex/using-git-worktrees-codex"><img src="https://agentmods.dev/badge/skills/mzored/superpowers-cc-to-codex/using-git-worktrees-codex.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.00038 | $0.01229 |
| Opus 5.5 | $0.00015 | $0.00492 |
| Sonnet 5.5 | $0.00008 | $0.00246 |
| Haiku 4.5 | $0.00004 | $0.00123 |
Grade A, and why
using-git-worktrees-codex 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 2mo 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.
How it starts
The opening of the file, as written. The whole thing — 198 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Using Git Worktrees
Overview
Git worktrees create isolated workspaces sharing the same repository, allowing work on multiple branches simultaneously without switching.
Core principle: Systematic directory selection + safety verification = reliable isolation.
Announce at start: "I'm using the using-git-worktrees skill to set up an isolated workspace."
Directory Selection Process
Follow this priority order:
1. Check Existing Directories
# Check in priority order
ls -d .worktrees 2>/dev/null # Preferred (hidden)
ls -d worktrees 2>/dev/null # Alternative
If found: Use that directory. If both exist, .worktrees wins.
2. Check CLAUDE.md
grep -i "worktree.*director" CLAUDE.md 2>/dev/null
If preference specified: Use it without asking.
3. Ask User
If no directory exists and no CLAUDE.md preference:
No worktree directory found. Where should I create worktrees?
1. .worktrees/ (project-local, hidden)
2. ~/.config/superpowers/worktrees/<project-name>/ (global location)
Which would you prefer?
Safety Verification
For Project-Local Directories (.worktrees or worktrees)
MUST verify directory is ignored before creating worktree:
# Check if directory is ignored (respects local, global, and system gitignore)
git check-ignore -q .worktrees 2>/dev/null || git check-ignore -q worktrees 2>/dev/null
If NOT ignored:
Fix broken things immediately:
- Add appropriate line to .gitignore
- Commit the change
- Proceed with worktree creation
Why critical: Prevents accidentally committing worktree contents to repository.
For Global Directory (~/.config/superpowers/worktrees)
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.
- 2mo ago First seen · 198 lines · 38 tokens per session scan A d1331dfd63ca
using-git-worktrees-codex is a skill published in the GitHub repository mzored/superpowers-cc-to-codex (7 stars, last pushed 6mo ago), licensed MIT. It adds 38 tokens to every session and 1,229 once invoked, about $0.0002 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.
using-git-worktrees-codex compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| using-git-worktrees-codexmzored/superpowers-cc-to-codex | Skill | 7 | 6mo ago | MIT | A | 38 | Claude Code |
| workflowclaude-world/director-mode-lite | Skill | 80 | 16d ago | MIT | A | 52 | Claude Code |
| smart-commitclaude-world/director-mode-lite | Skill | 80 | 16d ago | MIT | A | 49 | Claude Code |
| handoff-claudeclaude-world/director-mode-lite | Skill | 80 | 16d ago | MIT | A | 51 | Claude Code |
| document-releaseDollarDill/beads-superpowers | Skill | 32 | 7d ago | MIT | A | 103 | Claude Code |
| finishing-a-development-branchDollarDill/beads-superpowers | Skill | 32 | 7d ago | MIT | A | 44 | Claude Code |
| pr-contributionxobotyi/cc-foundry | Skill | 23 | 6d ago | MIT | A | 51 | Claude Code |