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/airmcp-com/mcp-standards/workflowgit clone --depth 1 https://github.com/airmcp-com/mcp-standardsWrote 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/airmcp-com/mcp-standards/workflow)<a href="https://agentmods.dev/commands/airmcp-com/mcp-standards/workflow"><img src="https://agentmods.dev/badge/commands/airmcp-com/mcp-standards/workflow.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.00013 | $0.00692 |
| Opus 5 | $0.00006 | $0.00346 |
| Sonnet 5 | $0.00003 | $0.00138 |
| Haiku 4.5 | $0.00001 | $0.00069 |
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 4d 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.
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.
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
})
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.
- 4d ago First seen · 115 lines · 13 tokens per session scan A 1e2956e4a40f
flow-nexus-workflow is a command published in the GitHub repository airmcp-com/mcp-standards (3 stars, last pushed 9mo 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.
Other commands, from other repositories
merge
Finish a PR properly: every check green, every review addressed — human and bot — then merge and clean up.
pr
Prepare and open a pull request the senior way: gate, template, scrubbed, everything visible.
spec
Spec-first design: a gap-closing interview that produces a complete spec, with a quality controller that blocks until every section is answered and every question resolved.
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.
tdd
Test-driven development with tests that actually catch breaks: red before green, name the break each test catches, and the mutation check before done.
todo
The quality-gated task list: tasks with real descriptions, testable acceptance criteria, and evidence — a task only closes when the controller agrees it is done.