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/shipgit 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/ship)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/ship"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/ship.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.00011 | $0.03269 |
| Opus 5 | $0.00005 | $0.01635 |
| Sonnet 5 | $0.00002 | $0.00654 |
| Haiku 4.5 | $0.00001 | $0.00327 |
Grade A, and why
ship 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 5d 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 — 570 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quick Ship Command
Ship small features/fixes fast without full PRD overhead, with optional worktree isolation.
Purpose
For small changes that don't need full PRD:
- Bug fixes
- Small UI tweaks
- Dependency updates
- Minor refactors
- Quick experiments
NEW in v0.4.4: Automatic context detection - run from Main OR from worktree directly!
v0.4.3: Support for worktree isolation with --worktree flag.
Context Detection (Auto)
The /ship command automatically detects where you run it from:
From Main Repository
# Working directory: ~/Documents/watchora
$ /ship "Fix auth bug"
→ Behavior: Works on Main (default)
→ Optional: Add --worktree to use hotfix worktree
From Hotfix Worktree
# Working directory: ~/Documents/watchora/worktrees/hotfix
$ /ship "Fix auth bug"
→ Behavior: Automatically uses worktree (no --worktree needed!)
→ Syncs, locks, creates branch, works in current directory
Key Point: If you have a dedicated Cursor window open on worktrees/hotfix/, you can use /ship directly from there!
When to Use
Use Quick Ship for:
- Features < 4 hours
- Single developer work
- Clear scope, no unknowns
- Low risk changes
Use Full PRD for:
- Features > 1 day
- Multiple developers
- Unclear requirements
- High-risk changes
- Customer-facing features
Usage
# From Main: Work on Main (quick, simple)
/ship "Fix login button alignment"
# From Main: With worktree isolation (safer, larger fixes)
/ship "Refactor auth module" --worktree
# From Worktree: Auto-detects worktree context
cd worktrees/hotfix/
/ship "Fix auth bug" # Automatically uses worktree!
# Manage active fix (works from anywhere)
/ship --complete # Finish and merge
/ship --abort # Cancel fix
/ship --status # Show current status
/ship --pause # Pause current fix
/ship --resume # Resume paused fix
# Migrate from Main to worktree
/ship --to-worktree # Move current fix to 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.
- 5d ago First seen · 570 lines · 11 tokens per session scan A 85f7a889fa64
ship is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 11 tokens to every session and 3,269 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.
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.
status
The state of play, computed fresh: branch, dirty files, the active sprint, open work, index freshness.