list-flows

A command for listing Postman Flows, which are visual workflows for working with APIs, in a selected workspace.

In plain words
What is it for?
Use it to list flows, filter them by name, and resolve a matching flow to its 24-character ID.
Why use it?
It avoids manually searching for flows and helps identify the exact ID needed for later actions.

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/list-flows
Clone the repo
git clone --depth 1 https://github.com/Postman-Devrel/postman-claude-code-plugin
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 240 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.00019 $0.00240
Opus 5 $0.00010 $0.00120
Sonnet 5 $0.00004 $0.00048
Haiku 4.5 $0.00002 $0.00024

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

Security

Grade A, and why

list-flows 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/list-flows.md · 22 lines

What it actually says

List Postman Flows in a workspace using the Postman CLI. Follow the list-flows skill.

Inputs (from the user's message)

  • The workspace ID (ask if unknown)
  • Optionally a name/pattern to filter by

Steps

  1. Ensure you have a workspace ID; ask which workspace if not.
  2. Run:
    POSTMAN_CLI_SOURCE=claude-code-plugin postman flows list --workspace <workspaceId>
    
    Narrow with --filter "<name>" when resolving a specific flow; use --sort name / --paginate as needed.
  3. Report flow names + IDs (and recent status where shown). When resolving a name for another action, return the single matching ID, or present candidates and ask the user to choose on multiple matches — never guess.

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 · 22 lines · 19 tokens per session scan A 0b80ab04d040

Subscribe to this mod's changes

list-flows is a command published in the GitHub repository Postman-Devrel/postman-claude-code-plugin (38 stars, last pushed 28d ago), licensed Apache-2.0. It adds 19 tokens to every session and 240 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

routine

Execute one maintenance routine defined in scv/routines/ .md (task + guardrails + exit-criteria contract), or list defined routines. SCV never schedules — pair with host features like /loop or cron yourself. Use whenever the user asks to run a recurring maintenance task, or asks what routines exist — not only when…

wookiya1364/scv-claude-code · 75 tokens

workspace

Set up or change this repo's place in a multi-repo SCV workspace: join an umbrella as a child, create an umbrella (root), check status, or detach. Friendly — no long flags to remember. Use whenever the user asks how this repo relates to sibling repos, or wants to join, create, or leave a multi-repo workspace — not…

wookiya1364/scv-claude-code · 83 tokens

incident

Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.

HigorAlves/orc · 54 tokens

t800-onboard

Для чата с новичками. Показывает, что настроено в Cursor (global + local), и что умеет отдел T-800.

Khar-AG/t-800-agent · 0 tokens

evidence

Collect browser evidence scoped to a ticket (or shared context) and deliver it — evidence packet, then upload to the ticket or keep local (always asks). For proving a ticket's behavior without a code diff/PR. Workspace-aware.

HigorAlves/orc · 47 tokens

analyze-dependabot

分析 Dependabot 安全告警并创建安全分析文档.

ModelEngine-Group/fit-framework · 19 tokens