learn

A command that searches Postman’s official Learning Center, Postman’s online documentation and how-to guide. It answers questions about using the Postman product.

In plain words
What is it for?
It helps explain Postman features and workflows, answer how-to questions, and provide cited guidance when the Postman MCP server is running in Full mode.
Why use it?
It provides product guidance from the official documentation instead of searching the user’s own collections, workspaces, or specifications.

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/learn
Clone the repo
git clone --depth 1 https://github.com/Postman-Devrel/postman-claude-code-plugin
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 885 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.00032 $0.00885
Opus 5 $0.00016 $0.00443
Sonnet 5 $0.00006 $0.00177
Haiku 4.5 $0.00003 $0.00089

Measured yesterday against content hash 99fab719f2bf, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

learn 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 yesterday.

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/learn.md · 70 lines

How it starts

The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Learn Postman

Answer "how do I..." questions about the Postman product by searching the official Postman Learning Center (https://learning.postman.com). Explain features, walk through workflows, and cite authoritative sources.

Use this to learn about Postman itself — not to search the user's own collections, workspaces, or specs (that's /postman:search).

Prerequisites

This command uses searchLearningCenter, which is only exposed when the Postman MCP Server runs in Full mode (POSTMAN_MCP_MODE=mcp, the default). It is not available in minimal or code mode.

  • If MCP tools aren't available at all, tell the user: "Run /postman:setup to configure the Postman MCP Server."
  • If searchLearningCenter specifically is missing, call getEnabledTools to confirm the active tool set, then tell the user: "Searching the Learning Center requires Full mode. Unset POSTMAN_MCP_MODE (or set it to mcp) and restart Claude Code."

Workflow

Step 1: Search

Call searchLearningCenter with a focused query derived from the user's question. Prefer the product vocabulary from postman-knowledge (mock server, environment, monitor, collection variable, etc.) over the user's exact phrasing.

  • Turn a broad request into a specific query — "how to create a mock server", "write a test script", "set a collection variable", "schedule a monitor".
  • If results are thin or off-target, refine: try a different feature term, split a multi-part question into separate searches, or broaden a narrow query.

Step 2: Synthesize

Read the returned passages and compose a direct answer to the user's question. Do not just dump raw results.

  • Lead with the answer or the concrete steps.
  • Keep steps in the order the user would perform them.
  • If the docs reveal a better or officially recommended workflow than what the user asked, surface it.
  • Always cite the source URLs the tool returns so the user can read more.

Step 3: Connect to the Plugin

When a workflow maps to a plugin command, point the user there so they can act immediately:

Read the full file on GitHub · 70 lines

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. yesterday First seen · 70 lines · 32 tokens per session scan A 99fab719f2bf

Subscribe to this mod's changes

learn 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 32 tokens to every session and 885 once invoked, about $0.0002 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