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/rungit 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/run)<a href="https://agentmods.dev/commands/airmcp-com/mcp-standards/run"><img src="https://agentmods.dev/badge/commands/airmcp-com/mcp-standards/run.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.00357 |
| Opus 5 | $0.00000 | $0.00179 |
| Sonnet 5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
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 2d 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 run — 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.
What it actually says
stream-chain run
Execute a custom stream chain with your own prompts.
Usage
claude-flow stream-chain run <prompt1> <prompt2> [...] [options]
Minimum 2 prompts required for chaining.
Options
--verbose- Show detailed execution information--timeout <seconds>- Timeout per step (default: 30)--debug- Enable debug mode
How It Works
Each prompt in the chain receives the complete output from the previous step as context, enabling complex multi-step workflows.
Examples
Basic Chain
claude-flow stream-chain run \
"Write a function" \
"Add tests for it"
Complex Workflow
claude-flow stream-chain run \
"Analyze the authentication system" \
"Identify security vulnerabilities" \
"Propose fixes with priority levels" \
"Implement the critical fixes" \
"Generate tests for the fixes"
With Options
claude-flow stream-chain run \
"Complex analysis task" \
"Detailed implementation" \
--timeout 60 \
--verbose
Context Preservation
The output from each step is injected into the next prompt:
Step 1: "Write a sorting function"
Output: [function code]
Step 2 receives: "Previous step output:
[function code]
Next step: Optimize for performance"
Best Practices
- Clear Instructions: Make each prompt specific
- Logical Flow: Order prompts in logical sequence
- Appropriate Timeouts: Increase for complex tasks
- Verification: Add verification steps in chain
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.
- 2d ago First seen · 70 lines · 0 tokens per session scan A 554410e9afc1
run is a command published in the GitHub repository airmcp-com/mcp-standards (3 stars, last pushed 9mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 357 tokens. A static security scan graded it A with 0 findings. It is 100% identical to run, 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.
debug
Systematic debugging: root cause before any fix, one hypothesis at a time, and a three-strikes rule that questions the architecture instead of stacking patches.
index
The code index: build it, then find, search, refs, outline, and impact instead of grepping blind.
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.