A custom chain of prompts in which each step receives the previous step's output as context.

Use it to chain work such as analyzing authentication, identifying security issues, proposing fixes, implementing them, and generating tests.

It keeps information flowing through a multi-step task instead of making you repeat earlier results in every instruction.

run — Command for Claude Code by proffesor-for-testing/agentic-qe

Install

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.

Clone the repo

git clone --depth 1 https://github.com/proffesor-for-testing/agentic-qe

Made for: Claude Code.

Or install agentic-qe, the plugin that ships this one along with the rest of its 41 skills, 143 commands, 10 agents, 10 hooks, 1 plugin.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/proffesor-for-testing/agentic-qe/run/github.svg)](https://agentmods.dev/commands/proffesor-for-testing/agentic-qe/run)

Your own site

<a href="https://agentmods.dev/commands/proffesor-for-testing/agentic-qe/run"><img src="https://agentmods.dev/badge/commands/proffesor-for-testing/agentic-qe/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/proffesor-for-testing/agentic-qe/run"><img src="https://agentmods.dev/badge/commands/proffesor-for-testing/agentic-qe/run.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 357 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.5	$0.00000	$0.00143
Sonnet 5.5	$0.00000	$0.00071
Haiku 4.5	$0.00000	$0.00036

Measured 6d ago against content hash 750a7432cd19, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 6d 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.

Origin

Copies of this mod

4 near-identical copies found in the catalogue:

run — 100% identical, 138 lines differ
run — 100% identical, 138 lines differ
run — 100% identical, 138 lines differ
run — 100% identical, 142 lines differ

.claude/commands/stream-chain/run.md · 70 lines

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

Changes

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.

6d ago First seen · 70 lines · 0 tokens per session scan A 750a7432cd19

Subscribe to this mod's changes

run is a command published in the GitHub repository proffesor-for-testing/agentic-qe (504 stars, last pushed yesterday), 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-11.

Productivity agenticqe agenticsfoundation agents quality-engineering

run