get-flow-run

A read-only command for examining one Postman Flow run by its run ID. It shows the run status, block-level logs, and the block that failed, if any.

In plain words
What is it for?
Use it to inspect a run summary, view detailed logs, or filter the results to one block.
Why use it?
It helps locate the exact step and reason behind a failed or incomplete flow execution.

Command

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.

agentmods
npx agentmods add commands/postman-devrel/postman-claude-code-plugin/get-flow-run
Clone the repo
git clone --depth 1 https://github.com/Postman-Devrel/postman-claude-code-plugin
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 238 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00238
Opus 5 $0.00010 $0.00119
Sonnet 5 $0.00004 $0.00048
Haiku 4.5 $0.00002 $0.00024

Measured 2d ago against content hash 62c9a4d2f5a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

get-flow-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.

commands/get-flow-run.md · 23 lines

What it actually says

Inspect a specific Postman Flow run using the Postman CLI. Follow the get-flow-run skill.

Inputs (from the user's message)

  • The Run ID (the x-run-id that trigger-flow reported; ask if unknown)
  • Optionally a block ID to focus on

Steps

  1. Take the Run ID.
  2. Run a summary, then add --logs for detail:
    POSTMAN_CLI_SOURCE=claude-code-plugin postman flows get-run --run-id <runId>
    POSTMAN_CLI_SOURCE=claude-code-plugin postman flows get-run --run-id <runId> --logs
    
    Narrow to a block with --filter <blockId>.
  3. Report which block failed and why and the run status.

Read-only: no confirmation needed. Prefix CLI calls with POSTMAN_CLI_SOURCE=claude-code-plugin. Reuse existing postman login credentials.

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.

  1. 2d ago First seen · 23 lines · 20 tokens per session scan A 62c9a4d2f5a4

Subscribe to this mod's changes

get-flow-run is a command published in the GitHub repository Postman-Devrel/postman-claude-code-plugin (38 stars, last pushed 27d ago), licensed Apache-2.0. It adds 20 tokens to every session and 238 once invoked, about $0.0001 per session on Opus 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-08-30.

Related

Other commands, from other repositories