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 commands/yassinello/claude-plugin-prd-workflow/worktreegit clone --depth 1 https://github.com/Yassinello/claude-plugin-prd-workflowWrote 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/commands/yassinello/claude-plugin-prd-workflow/worktree)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/worktree"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/worktree.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 | $0.00016 | $0.02417 |
| Opus 5 | $0.00008 | $0.01208 |
| Sonnet 5 | $0.00003 | $0.00483 |
| Haiku 4.5 | $0.00002 | $0.00242 |
Grade A, and why
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 4d 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 — 422 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Worktree Management Command
Centralized management for fixed worktrees (hotfix, debug) with intelligent sync.
Purpose
Manage permanent worktrees for quick fixes and debugging sessions:
- 🔧 hotfix/ - Quick fixes and UI tweaks
- 🐛 debug/ - Debugging sessions with modifications
Commands
Setup
/worktree setup
Initial setup of fixed worktrees:
- Creates
worktrees/hotfix/on branchhotfix - Creates
worktrees/debug/on branchdebug - Configures lock files
- Sets up Git hooks (optional)
What happens:
1. Create worktrees/ directory if needed
2. git worktree add worktrees/hotfix hotfix
3. git checkout -b hotfix main # Parking branch
4. git worktree add worktrees/debug debug
5. git checkout -b debug main # Parking branch
6. Create .claude-lock files
7. git checkout main # Return to main
Sync
/worktree sync
/worktree sync --force
/worktree sync hotfix
/worktree sync debug
Sync all or specific worktrees with main:
- Intelligent sync strategy (Option C)
- Skips locked worktrees (fix in progress)
- Shows recent changes preview
- Force sync bypasses thresholds
Sync Strategy (Intelligent):
- 0 commits behind: ✅ Nothing to do
- 1-10 commits: 🔄 Silent auto-sync
- 10-50 commits: ⚠️ Propose sync with preview
- 50+ commits: ❌ Force sync (required)
Status
/worktree status
/worktree status --verbose
/worktree status hotfix
Show status of all worktrees:
- Lock status (idle/in_progress)
- Current branch
- Sync status (commits behind main)
- Last used timestamp
- Available actions
List
/worktree list
List all worktrees (including PRD worktrees):
- Path and branch
- Status
- Sync info
Prune
/worktree prune
/worktree prune --force
Clean up obsolete worktrees:
- Remove merged PRD worktrees
- Clean orphaned worktree directories
- Reset fixed worktrees to clean state (if idle)
Workflow
Initial Setup (Once)
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.
- 4d ago First seen · 422 lines · 16 tokens per session scan A b8a209c72368
worktree is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 16 tokens to every session and 2,417 once invoked, about $0.0001 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 commands, from other repositories
brooks-debt
Run a Brooks-Lint tech debt assessment.
brooks-health
Run a Brooks-Lint codebase health dashboard across all four dimensions.
plan
Turn an approved spec into an implementation plan an engineer with zero context could execute — with a quality controller that blocks placeholders and hollow tasks.
simplify
The over-engineering review: five tags (delete, stdlib, native, yagni, shrink), a mandatory replacement per finding, and a real null result when there is nothing to cut.
audit
Onboard an existing codebase: every domain's checks over the whole tree, then a triaged plan to bring it in line.
test
Run the repository's actual test suite: every ecosystem's canonical runner — NOT run is never green.