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/hotfixgit 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/hotfix)<a href="https://agentmods.dev/commands/yassinello/claude-plugin-prd-workflow/hotfix"><img src="https://agentmods.dev/badge/commands/yassinello/claude-plugin-prd-workflow/hotfix.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.00018 | $0.01024 |
| Opus 5 | $0.00009 | $0.00512 |
| Sonnet 5 | $0.00004 | $0.00205 |
| Haiku 4.5 | $0.00002 | $0.00102 |
Grade A, and why
hotfix 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hotfix Command
Alias for /ship --worktree - always uses worktree isolation for quick fixes.
NEW in v0.4.4: Works seamlessly from Main OR from worktree directly thanks to automatic context detection!
Purpose
For developers who prefer worktree isolation by default:
- Shorter to type than
/ship --worktree - Always works in dedicated worktree
- Same workflow as
/shipbut with guaranteed isolation - Can be launched from Main OR from worktree directly
Usage
# From Main: Basic usage
/hotfix "Fix login button alignment"
# Equivalent to:
/ship "Fix login button alignment" --worktree
# From Worktree: Auto-detects context (NEW!)
cd worktrees/hotfix/
/hotfix "Fix login button" # Works seamlessly!
# All /ship options work (from anywhere)
/hotfix --complete # Finish fix
/hotfix --abort # Cancel fix
/hotfix --status # Check status
/hotfix --pause # Pause fix
/hotfix --resume # Resume fix
When to Use
Use /hotfix when:
- ✅ You prefer worktree isolation by default
- ✅ Refactoring or multi-file changes
- ✅ Want separate Cursor window
- ✅ > 100 lines of changes expected
Use /ship (without --worktree) when:
- ✅ Quick typo fix (1-2 files)
- ✅ < 50 lines of changes
- ✅ < 15 minutes work
- ✅ Very low risk change
Workflow
Step 1: Start Fix
$ /hotfix "Refactor authentication module"
🔍 Checking worktree hotfix/...
🔄 Syncing worktree (3 commits behind)...
✅ Synced with main
✅ Started in worktrees/hotfix/
📝 Branch: hotfix/refactor-auth-module
🔒 Locked worktree
💻 Open in new window: code worktrees/hotfix/
Step 2: Work in Isolation
Work in worktrees/hotfix/:
- Complete isolation from Main
- No size/time warnings
- Can open in separate Cursor window
Step 3: Complete
$ /hotfix --complete
✅ Committed & pushed
📤 PR created
✅ Auto-merged (checks passed)
🧹 Cleaned up
↩️ Returned to Main
Comparison: /hotfix vs /ship
| Aspect | /hotfix | /ship |
|---|---|---|
| Default | Worktree | Main |
| Isolation | Always | Optional (--worktree) |
| Best for | Refactors, multi-file | Quick fixes, typos |
| Warnings | None | Size/time warnings |
| Main usage | Never touches Main | Works on Main |
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 · 173 lines · 18 tokens per session scan A 94cdb34e1567
hotfix is a command published in the GitHub repository Yassinello/claude-plugin-prd-workflow (12 stars, last pushed 9mo ago), licensed MIT. It adds 18 tokens to every session and 1,024 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-health
Run a Brooks-Lint codebase health dashboard across all four dimensions.
brooks-debt
Run a Brooks-Lint tech debt assessment.
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.