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/run)<a href="https://agentmods.dev/commands/monoes/monomind/run"><img src="https://agentmods.dev/badge/commands/monoes/monomind/run/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/run"><img src="https://agentmods.dev/badge/commands/monoes/monomind/run.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.00029 | $0.00864 |
| Opus 5.5 | $0.00012 | $0.00346 |
| Sonnet 5.5 | $0.00006 | $0.00173 |
| Haiku 4.5 | $0.00003 | $0.00086 |
Grade A, and why
stream-chain:run 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 — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stream-Chain Run Mode
Execute custom multi-step workflows with your own prompt sequence. Each step's full output becomes context for the next.
How to Invoke
In Claude Code, activate run mode:
Skill("stream-chain:run")
Then provide your chain directly:
"Run a stream chain:
- Write a sorting function
- Add tests for it
- Optimize it for performance"
How Context Flows
Each step receives the complete output of all previous steps:
Step 1: "Write a sorting function"
Output: [function code]
Step 2 receives:
Previous output: [function code]
Task: "Add comprehensive tests"
Step 3 receives:
Previous output: [function + tests]
Task: "Optimize for performance"
Examples
Basic Development Chain
"Stream chain:
- Write a user authentication function
- Add input validation and error handling
- Create unit tests with edge cases"
Security Audit Workflow
"Stream chain for the
src/auth/module:
- Analyze for security vulnerabilities
- Categorize issues by severity (critical/high/medium/low)
- Propose fixes with implementation priority
- Generate security test cases"
Code Refactoring Chain
"Stream chain:
- Identify code smells in
src/directory- Create refactoring plan with specific changes
- Apply refactoring to top 3 priority items
- Verify refactored code maintains original behavior"
Data Processing Pipeline
"Stream chain:
- Extract data from API responses in
handlers/- Transform data into normalized format
- Validate data against schema
- Generate data quality report"
Code Migration Workflow
"Stream chain for migrating Vue 2 to Vue 3:
- Analyze codebase dependencies and breaking changes
- Create migration plan with risk assessment
- Generate modernized code for high-priority components
- Create migration tests
- Document migration steps and rollback procedures"
Best Practices
1. Clear, Specific Prompts
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 · 151 lines · 29 tokens per session scan A ec10d9dd247c
stream-chain:run is a command published in the GitHub repository monoes/monomind (23 stars, last pushed yesterday), licensed Apache-2.0. It adds 29 tokens to every session and 864 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
test
Design or run focused test validation for a task, bug, or diff.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
flutter-test
Run Flutter/Dart tests, report failures, and incrementally fix test issues. Covers unit, widget, golden, and integration tests.
build-fix
Systematically investigate and fix build errors, TypeScript errors, or test failures with minimal diffs.
test-coverage
Analyze and improve test coverage.
verify
Run verification loop to validate implementation.