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 skills add Postman-Devrel/postman-claude-code-plugin --skill flowsgit clone --depth 1 https://github.com/Postman-Devrel/postman-claude-code-pluginWrote 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/skills/postman-devrel/postman-claude-code-plugin/flows)<a href="https://agentmods.dev/skills/postman-devrel/postman-claude-code-plugin/flows"><img src="https://agentmods.dev/badge/skills/postman-devrel/postman-claude-code-plugin/flows/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/skills/postman-devrel/postman-claude-code-plugin/flows"><img src="https://agentmods.dev/badge/skills/postman-devrel/postman-claude-code-plugin/flows.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.00116 | $0.02502 |
| Opus 5.5 | $0.00046 | $0.01001 |
| Sonnet 5.5 | $0.00023 | $0.00500 |
| Haiku 4.5 | $0.00012 | $0.00250 |
Grade A, and why
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 1mo 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.
How it starts
The opening of the file, as written. The whole thing — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Postman Flows
Overview
Listing flows, running them, deploying them so they become callable, and
tracing a failed run to the block that caused it — all through
postman flows.
Core knowledge
A flow is a graph of blocks, not a script. That single fact drives the rest of this skill: a flow has two independent execution paths, and its HTTP response describes one block rather than the whole graph, so debugging takes a different command than running.
Local file vs deployed artifact
run and trigger are not two ways to execute one flow. Postman Flows has
two Native Git modes, and they are isolated from each other:
- Cloud View (the default) syncs flows to Postman Cloud, which is what
makes them shareable and deployable — so Cloud View is the only side
deploy,trigger,update,list-runsandget-runever address. - Local View stores flows as JSON in a local Git repo, updated as they are edited. Those flows cannot be shared or deployed, have no snapshots, and are isolated from the flows in Cloud View.
flows run <path> |
flows trigger <flowId> |
|
|---|---|---|
| Executes | a flow JSON file on this machine | the cloud-deployed flow, via its webhook |
| Returns | status, output, test results, exit code | Run ID + HTTP status + response body |
| Observability | own stdout, --output, --reporters |
get-run, per block |
| Environment file | -e/--environment |
not supported |
run exits nonzero on failure, which is what lets a CI job gate on it.
trigger goes through the real webhook URL, so it exercises the deployed path
end-to-end — auth and trigger configuration included — and registers a cloud
run that get-run can explain block by block.
postman init scaffolds postman/flows/, and Postman's flows run examples
use that path. Note what puts files there: the Git-connected Flows experience
is desktop-app only, so postman/flows/*.json is written by the desktop
app's Local View, not by the CLI — workspace push/pull carry no flows
handling whatever else they sync. Don't tell a user to workspace pull to
obtain a flow file.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 213 lines · 116 tokens per session scan A 91c290a8be5f
flows is a skill published in the GitHub repository Postman-Devrel/postman-claude-code-plugin (41 stars, last pushed 21d ago), licensed Apache-2.0. It adds 116 tokens to every session and 2,502 once invoked, about $0.0005 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-09-20.
Other skills, from other repositories
postman
Full API lifecycle management through Postman. Sync OpenAPI specs to collections, generate typed client code, run API tests, create mock servers, publish documentation, audit security against OWASP Top 10, and discover APIs across workspaces. Requires the Postman MCP Server. Use this skill when the user mentions…
postman-api-readiness
Analyze any API for AI agent compatibility. Scans OpenAPI specs across 8 pillars (48 checks), scores agent-readiness 0-100, and provides prioritized fix recommendations. Use this skill when the user asks: "Is my API agent-ready?", "Scan my API", "Analyze my OpenAPI spec", "What's wrong with my API for AI agents?"…
stripe-projects
Provision SaaS services + sync creds via Stripe Projects.
django-storages-s3
Use when configuring Django to store static and media files on AWS S3 with django-storages. Invoke when working with the STORAGES setting, S3 buckets, presigned URLs, CloudFront, or boto3-backed file storage in settings.py. Configures the Django 4.2+ STORAGES dict, public/private custom backends, presigned GET/POST…
websocket-engineer
Use when building real-time communication systems with WebSockets or Socket.IO. Invoke for bidirectional messaging, horizontal scaling with Redis, presence tracking, room management.
azure-eventhub-dotnet
Azure Event Hubs SDK for .NET. Use for high-throughput event streaming: sending events (EventHubProducerClient, EventHubBufferedProducerClient), receiving events (EventProcessorClient with checkpointing), partition management, and real-time data ingestion. Triggers: "Event Hubs", "event streaming"…