Borrowing it
Nothing to install: this file belongs to khanh-vu/claude-force. 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/khanh-vu/claude-force/main/.claude/commands/run-workflow.mdgit clone --depth 1 https://github.com/khanh-vu/claude-forceWrote 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/khanh-vu/claude-force/run-workflow)<a href="https://agentmods.dev/commands/khanh-vu/claude-force/run-workflow"><img src="https://agentmods.dev/badge/commands/khanh-vu/claude-force/run-workflow/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/commands/khanh-vu/claude-force/run-workflow"><img src="https://agentmods.dev/badge/commands/khanh-vu/claude-force/run-workflow.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.00006 | $0.00520 |
| Opus 5.5 | $0.00002 | $0.00208 |
| Sonnet 5.5 | $0.00001 | $0.00104 |
| Haiku 4.5 | $0.00001 | $0.00052 |
Grade A, and why
run-workflow 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Run Workflow Command
Execute a predefined workflow with multiple agents in sequence.
Available Workflows
1. full-stack-feature
Complete feature from architecture to deployment.
Agents (8):
- frontend-architect
- database-architect
- backend-architect
- python-expert
- ui-components-expert
- frontend-developer
- qc-automation-expert
- deployment-integration-expert
Use for: New features requiring both frontend and backend work.
2. frontend-only
Frontend-focused development workflow.
Agents (4):
- frontend-architect
- ui-components-expert
- frontend-developer
- qc-automation-expert
Use for: UI features, component libraries, client-side functionality.
3. backend-only
Backend API development workflow.
Agents (4):
- backend-architect
- database-architect
- python-expert
- qc-automation-expert
Use for: API endpoints, services, data processing.
4. documentation
Documentation generation workflow.
Agents (2):
- document-writer-expert
- api-documenter
Use for: Technical docs, API documentation, user guides.
Workflow Execution
For each agent in the workflow:
- Execute agent with full governance
- Validate output
- Confirm success before proceeding
- If failure, stop workflow and report
- Update progress in context file
- Proceed to next agent
Progress Tracking
The command will:
- Show current agent and progress (e.g., "Agent 3 of 8")
- Pause between agents for review (optional)
- Report completion status
- Provide summary of all artifacts
Example
/run-workflow full-stack-feature
This will execute all 8 agents in the full-stack workflow.
Options
/run-workflow full-stack-feature --no-pause
Run without pausing between agents.
/run-workflow frontend-only --start-from ui-components-expert
Resume workflow from specific agent.
Notes
- Requires
.claude/task.mdto be properly filled out - Each agent must pass validation before next one starts
- Can interrupt and resume later from same point
- Progress logged in
context_session_1.md
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 · 102 lines · 6 tokens per session scan A 6eea360cfd4b
run-workflow is a command published in the GitHub repository khanh-vu/claude-force (6 stars, last pushed 11mo ago), licensed MIT. It adds 6 tokens to every session and 520 once invoked, about $0.0000 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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
speckit.bug.fix
Apply the remediation from a bug assessment and record what was changed.
speckit.bug.test
Validate that a previously fixed bug is resolved and record the verification report.