What is flow-nexus-workflow?

A workflow automation command set for event-driven jobs, where events such as a code push can start a sequence of tasks. It uses message queues to run and coordinate those tasks.

Use it to create, start, monitor, list, and audit workflows; assign tasks to agents; and process inputs such as branches and commit IDs.

It removes the need to manually start, assign, and track multi-step processes, while keeping status and audit information available.

flow-nexus-workflow — Command by EarthmanWeb

Install

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.

agentmods

npx agentmods add commands/earthmanweb/claude-flow-plugin/workflow

Clone the repo

git clone --depth 1 https://github.com/EarthmanWeb/claude-flow-plugin

Made for: Claude Code.

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 692 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin 100% copy Near-identical to another mod in the catalogue.

Token cost

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.00013	$0.00692
Opus 5	$0.00006	$0.00346
Sonnet 5	$0.00003	$0.00138
Haiku 4.5	$0.00001	$0.00069

Measured 2d ago against content hash 1e2956e4a40f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

flow-nexus-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 2d 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.

Origin

This is a copy

100% identical to flow-nexus-workflow — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/commands/flow-nexus/workflow.md · 115 lines

How it starts

The opening of the file, as written. The whole thing — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Flow Nexus Workflows

Create and manage automated workflows with event-driven processing.

Create Workflow

mcp__flow-nexus__workflow_create({
  name: "CI/CD Pipeline",
  description: "Automated testing and deployment",
  steps: [
    { id: "test", action: "run_tests", agent: "tester" },
    { id: "build", action: "build_app", agent: "builder" },
    { id: "deploy", action: "deploy_prod", agent: "deployer" }
  ],
  triggers: ["push_to_main", "manual_trigger"]
})

Execute Workflow

mcp__flow-nexus__workflow_execute({
  workflow_id: "workflow_id",
  input_data: {
    branch: "main",
    commit: "abc123"
  },
  async: true // Execute via message queue
})

Monitor Workflows

// Get workflow status
mcp__flow-nexus__workflow_status({
  workflow_id: "id",
  include_metrics: true
})

// List workflows
mcp__flow-nexus__workflow_list({
  status: "running",
  limit: 10
})

// Get audit trail
mcp__flow-nexus__workflow_audit_trail({
  workflow_id: "id",
  limit: 50
})

Agent Assignment

mcp__flow-nexus__workflow_agent_assign({
  task_id: "task_id",
  agent_type: "coder",
  use_vector_similarity: true // AI-powered matching
})

Queue Management

mcp__flow-nexus__workflow_queue_status({
  include_messages: true
})

Common Workflow Patterns

CI/CD Pipeline

mcp__flow-nexus__workflow_create({
  name: "Deploy Pipeline",
  steps: [
    { action: "lint", parallel: true },
    { action: "test", parallel: true },
    { action: "build", depends_on: ["lint", "test"] },
    { action: "deploy", depends_on: ["build"] }
  ],
  triggers: ["github_push"]
})

Data Processing

mcp__flow-nexus__workflow_create({
  name: "ETL Pipeline",
  steps: [
    { action: "extract_data", agent: "data_extractor" },
    { action: "transform_data", agent: "transformer" },
    { action: "load_data", agent: "loader" },
    { action: "validate", agent: "validator" }
  ],
  triggers: ["schedule:0 2 * * *"] // Daily at 2 AM
})

Read the full file on GitHub · 115 lines

Changes

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.

2d ago First seen · 115 lines · 13 tokens per session scan A 1e2956e4a40f

Subscribe to this mod's changes

flow-nexus-workflow is a command published in the GitHub repository EarthmanWeb/claude-flow-plugin (2 stars, last pushed 7mo ago), licensed MIT. It adds 13 tokens to every session and 692 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to flow-nexus-workflow, differing in 0 lines, and is treated as a copy.

Git and workflow Productivity

flow-nexus-workflow