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/monoes/monomindWrote 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/monoes/monomind/pipeline)<a href="https://agentmods.dev/commands/monoes/monomind/pipeline"><img src="https://agentmods.dev/badge/commands/monoes/monomind/pipeline/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/monoes/monomind/pipeline"><img src="https://agentmods.dev/badge/commands/monoes/monomind/pipeline.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.00033 | $0.00652 |
| Opus 5.5 | $0.00013 | $0.00261 |
| Sonnet 5.5 | $0.00007 | $0.00130 |
| Haiku 4.5 | $0.00003 | $0.00065 |
Grade A, and why
stream-chain: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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stream-Chain Pipeline Mode
Execute predefined multi-step workflows where each step's output flows into the next as context.
How to Invoke
In Claude Code, activate pipeline mode:
Skill("stream-chain:pipeline")
Then tell Claude which pipeline to run and on what target:
"Run the analysis pipeline on the
src/auth/directory." "Run the refactor pipeline onUserService.ts."
Available Pipelines
analysis
Comprehensive codebase analysis and improvement identification.
Steps:
- Map directory structure and identify main components
- Identify potential improvements and issues
- Generate actionable improvement report with priorities
When to use: New codebase onboarding, technical debt assessment, architecture review, code quality audits.
refactor
Systematic code refactoring with prioritization.
Steps:
- Find code that would benefit from refactoring
- Create prioritized refactoring plan with specific changes
- Provide refactored code for top 3 priorities
When to use: Technical debt reduction, code quality improvement, design pattern implementation.
test
Comprehensive test generation with coverage analysis.
Steps:
- Identify areas lacking test coverage
- Design test cases for critical functions
- Generate unit test implementations with assertions
When to use: Increasing test coverage, TDD workflow support, regression test creation.
optimize
Performance optimization with profiling and implementation.
Steps:
- Profile codebase and identify performance bottlenecks
- Analyze bottlenecks and suggest optimization strategies
- Provide optimized implementations for main issues
When to use: Performance improvement, resource optimization, latency reduction.
Running Pipelines
After invoking the skill, direct Claude conversationally:
"Run the test pipeline on all files in
src/services/." "Run the optimization pipeline, focus on database query patterns." "Run the analysis pipeline, then the refactor pipeline on the findings."
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 · 117 lines · 33 tokens per session scan A f1116881ed19
stream-chain:pipeline is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 33 tokens to every session and 652 once invoked, about $0.0001 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-10-26.
Other commands, from other repositories
self-healing
Automatically detect and recover from errors without interrupting your flow.
prp-implement
Execute an implementation plan with rigorous validation loops.
test-coverage
Analyze and improve test coverage.
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.