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 agentmods add skills/postman-devrel/postman-claude-code-plugin/postman-knowledgenpx skills add Postman-Devrel/postman-claude-code-plugin --skill postman-knowledgegit clone --depth 1 https://github.com/Postman-Devrel/postman-claude-code-pluginWhat 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 | $0.00033 | $0.00734 |
| Opus 5 | $0.00016 | $0.00367 |
| Sonnet 5 | $0.00007 | $0.00147 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
postman-knowledge 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.
How it starts
The opening of the file, as written. The whole thing — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Postman Knowledge
Reference for Postman concepts and MCP tool selection. Use this context when working with Postman MCP tools to make better decisions.
Core Concepts
- Collection: A group of API requests organized in folders. The primary unit of work in Postman. Contains requests, examples, tests, and documentation.
- Environment: Key-value pairs (variables) scoped to a context (dev, staging, prod). Used to swap base URLs, auth tokens, and config without changing requests.
- Workspace: Container for collections, environments, and specs. Can be personal, team, or public.
- Spec (Spec Hub): An OpenAPI or AsyncAPI definition stored in Postman. Can generate collections and stay synced.
- Request: A single API call definition (method, URL, headers, body, tests).
- Response: A saved example response for a request. Used by mock servers and documentation.
- Folder: A grouping within a collection, typically by resource (e.g., "Users", "Orders").
- Tags: Labels on collections for categorization and search.
- Monitor: A scheduled collection runner that checks API health.
- Mock Server: A fake API that serves example responses from a collection.
Decision Guide
| Goal | Approach |
|---|---|
| Push code changes to Postman | Create/update spec in Spec Hub, then sync to collection |
| Consume a Postman API | Read collection + generate client code |
| Find an API | Use searchPostmanElements, then drill into details |
| Test an API | Run collection with runCollection |
| Create a fake API for frontend | Create mock server from collection with examples |
| Document an API | Analyze collection completeness, fill gaps, optionally publish |
| Audit API security | Run security checks against spec or collection |
| Learn how to use a Postman feature | Search Postman docs with searchLearningCenter (Full mode) |
MCP Tool Selection
Workspace operations: getWorkspaces, getWorkspace, createWorkspace
Collection CRUD: getCollections, getCollection, createCollection, putCollection, patchCollection, deleteCollection
Request/Response: getCollectionRequest, createCollectionRequest, updateCollectionRequest, getCollectionResponse, createCollectionResponse, updateCollectionResponse
Folder management: getCollectionFolder, createCollectionFolder, updateCollectionFolder
Spec Hub: getAllSpecs, getSpec, createSpec, getSpecDefinition, updateSpecFile, getSpecFiles
Sync: generateCollection, syncCollectionWithSpec, syncSpecWithCollection
Environments: getEnvironments, getEnvironment, createEnvironment, putEnvironment
Mocks: getMocks, getMock, createMock, publishMock, unpublishMock
Tests: runCollection
Docs: publishDocumentation, unpublishDocumentation
Search: searchPostmanElements , getTaggedEntities
Learning Center: searchLearningCenter (Full mode only — searches Postman product docs for how-to guidance)
User: getAuthenticatedUser
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.
- 2d ago First seen · 54 lines · 33 tokens per session scan A e0b30aaeb406
postman-knowledge is a skill published in the GitHub repository Postman-Devrel/postman-claude-code-plugin (38 stars, last pushed 27d ago), licensed Apache-2.0. It adds 33 tokens to every session and 734 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.
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?"…
taiyi-ui-design
TaiyiForge 第 4 阶段 — UI/UX 契约，产出 UI-DESIGN.md。四端通用。.
taiyi-evolve
TaiyiForge 辅助 — 实现后架构与文档同步（architecture-sync）。OpenCode / Claude / Codex / Cursor 通用。.
clarify
This skill should be used when user appears confused, frustrated, or shows misalignment between expectations and reality. Triggers on phrases like "I don't understand", "this doesn't make sense", "confused", "wait, shouldn't it...", "why is this happening", "I thought X did Y", contradictory statements, or frustration…
dialectic
Prove and counter-prove a statement using parallel agents to eliminate confirmation bias. Use when someone says "dialectic", "prove/disprove", "stress test this claim", "is this really true", "argue both sides", or when a statement needs objective analysis from opposing viewpoints.