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/nmime/motiv-buy/pipelinegit 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/pipeline)<a href="https://agentmods.dev/commands/nmime/motiv-buy/pipeline"><img src="https://agentmods.dev/badge/commands/nmime/motiv-buy/pipeline.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.00523 |
| Opus 5 | $0.00000 | $0.00262 |
| Sonnet 5 | $0.00000 | $0.00105 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
pipeline 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 yesterday.
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 pipeline — 21 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
stream-chain pipeline
Execute predefined pipelines for common development workflows.
Usage
claude-flow stream-chain pipeline <type> [options]
Available Pipelines
analysis
Code analysis and improvement pipeline.
claude-flow stream-chain pipeline analysis
Steps:
- Analyze current directory structure and identify main components
- Based on analysis, identify potential improvements and issues
- Generate detailed report with actionable recommendations
refactor
Automated refactoring workflow.
claude-flow stream-chain pipeline refactor
Steps:
- Identify code that could benefit from refactoring
- Create prioritized refactoring plan with specific changes
- Provide refactored code examples for top 3 priorities
test
Comprehensive test generation.
claude-flow stream-chain pipeline test
Steps:
- Analyze codebase and identify areas lacking test coverage
- Design comprehensive test cases for critical functions
- Generate unit test implementations with assertions
optimize
Performance optimization pipeline.
claude-flow stream-chain pipeline optimize
Steps:
- Profile codebase and identify performance bottlenecks
- Analyze bottlenecks and suggest optimization strategies
- Provide optimized implementations for main issues
Options
--verbose- Show detailed execution--timeout <seconds>- Timeout per step (default: 30)--debug- Enable debug mode
Examples
Run Analysis Pipeline
claude-flow stream-chain pipeline analysis
Refactor with Extended Timeout
claude-flow stream-chain pipeline refactor --timeout 60
Verbose Test Generation
claude-flow stream-chain pipeline test --verbose
Performance Optimization
claude-flow stream-chain pipeline optimize --debug
Output
Each pipeline generates:
- Step-by-step execution progress
- Success/failure status per step
- Total execution time
- Summary of results
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.
- yesterday First seen · 132 lines · 0 tokens per session scan A 55f5d4ca9110
pipeline is a command published in the GitHub repository nmime/motiv-buy (0 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 523 tokens. A static security scan graded it A with 0 findings. It is 100% identical to pipeline, differing in 21 lines, and is treated as a copy.
Other commands, from other repositories
verify
Run verification loop to validate implementation.
octo-loop
Your first output line MUST be: 🐙 Octopus Loop Mode.
octo-debug
Systematic debugging with methodical problem investigation.
dart-downstream-fix
fix a DART bug reported through gz-physics or Gazebo.
check-invariants
Runs only the tree CRDT invariant test battery in outl-core. Faster than /check, focused on what can break sync.
implement-fix-terminal-initialization-bugs
Implement OpenSpec change fix-terminal-initialization-bugs using specialized agent.