Borrowing it
Nothing to install: this file belongs to vibehat/claude-task-manager. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vibehat/claude-task-manager/master/.claude/commands/workflow-help.mdgit clone --depth 1 https://github.com/vibehat/claude-task-managerWrote 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/vibehat/claude-task-manager/workflow-help)<a href="https://agentmods.dev/commands/vibehat/claude-task-manager/workflow-help"><img src="https://agentmods.dev/badge/commands/vibehat/claude-task-manager/workflow-help.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.00000 | $0.00305 |
| Opus 5 | $0.00000 | $0.00152 |
| Sonnet 5 | $0.00000 | $0.00061 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
workflow-help 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.
What it actually says
Workflow Help - Structured Development Commands
Quick reference for the structured development workflow commands.
Usage: /workflow-help
Available Commands
🔍 Analysis Phase
/analyze-first [feature]- Analyze existing codebase before any planning/reuse-check [component]- Validate reuse opportunities before creating new files
📋 Planning Phase
/structured-plan [request]- Full 5-step structured planning workflow/plan-with-context [request]- Context-aware implementation planning after analysis
❓ Help
/workflow-help- Show this reference guide
Workflow Process
MANDATORY SEQUENCE:
- First:
/analyze-firstto understand existing code - Second:
/reuse-checkbefore creating anything new - Third:
/structured-planor/plan-with-contextfor implementation - Always: Validate compliance and justify any new file creation
Key Rules
- ❌ No new files without exhaustive reuse analysis
- ❌ No rewrites when refactoring is possible
- ❌ No generic advice - provide specific implementations
- ❌ No ignoring existing codebase architecture
- ✅ Extend existing services and components
- ✅ Consolidate duplicate code
- ✅ Reference specific file paths
- ✅ Provide migration strategies
Remember: Start with "COMPLIANCE CONFIRMED: I will prioritize reuse over creation" when using these commands.
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 · 44 lines · 0 tokens per session scan A 0e4d7b61d9c2
workflow-help is a command published in the GitHub repository vibehat/claude-task-manager (21 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 305 tokens. 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 commands, from other repositories
research-verify
Verify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'.
discuss
5-phase requirements-elicitation interview that produces an EARS-validated context/ .md.
sdd
Generate a Kiro-style spec triple — specs/ /{requirements,design,tasks}.md.
traceability-gen
Regenerate traceability.md from specs + plans + tests.
spec
Interview and write a spec for a change to this codebase, then list the policies it touches.
unity-migrate
Plan and execute Unity version or render pipeline migration — identifies deprecated APIs, package compatibility, and executes migration steps.