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.
git clone --depth 1 https://github.com/nmime/motiv-buyWrote 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/nmime/motiv-buy/workflow)<a href="https://agentmods.dev/commands/nmime/motiv-buy/workflow"><img src="https://agentmods.dev/badge/commands/nmime/motiv-buy/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/nmime/motiv-buy/workflow"><img src="https://agentmods.dev/badge/commands/nmime/motiv-buy/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.00013 | $0.00715 |
| Opus 5.5 | $0.00005 | $0.00286 |
| Sonnet 5.5 | $0.00003 | $0.00143 |
| Haiku 4.5 | $0.00001 | $0.00072 |
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 1mo 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 — 155 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 — 134 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.
- 1mo ago First seen · 134 lines · 13 tokens per session scan A 00ebdd0677e9
flow-nexus-workflow is a command published in the GitHub repository nmime/motiv-buy (0 stars, last pushed 9mo ago), licensed MIT. It adds 13 tokens to every session and 715 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to flow-nexus-workflow, differing in 155 lines, and is treated as a copy.
Other commands, from other repositories
dart-fix-ci
Command "dart-fix-ci" from dartsim/dart, covering required reading, workflow and output.
domains
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
access
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
check-release-health
Summarize the CI health of an OpenShift release using live data from the openshift-ci-mcp server.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
analyst
Use when performing local analyst review before pushing PR changes. Assesses code quality, impact analysis, and maintainability.