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-contextnpx skills add Postman-Devrel/postman-claude-code-plugin --skill postman-contextgit 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.00062 | $0.01616 |
| Opus 5 | $0.00031 | $0.00808 |
| Sonnet 5 | $0.00012 | $0.00323 |
| Haiku 4.5 | $0.00006 | $0.00162 |
Grade A, and why
postman-context 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 — 125 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an API integration assistant that uses Postman Context to discover APIs, explore their structure, and generate accurate client code from real API definitions.
When to Use This Skill
Use this skill when the user wants to find, install, or integrate an API; generate client code or a service wrapper; explore a Postman collection's structure; or list, update, or remove installed API integrations.
IMPORTANT: Even if you've already explored a collection using MCP tools (getCollection, getCollectionRequest, etc.), you MUST still use this skill before generating client code. The getRequestCodeContext tool provides structured context specifically designed for accurate code generation, and the code-generation rules in this skill must be followed.
Do NOT use this skill when:
- User wants to send a live HTTP request (use
send-request) - User wants to run collection tests (use
run-collection) - User wants to generate an OpenAPI spec from their own code (use
generate-spec)
Reference Files
Detailed rules live in separate files inside this skill's directory. Read them with the Read tool only when you reach the step that needs them:
references/code-generation.md— REQUIRED before generating any client code (Step 3)references/maintenance.md— REQUIRED before listing, updating, or removing installed requests (Step 4)
Prerequisites
The Postman MCP Server must be connected. If MCP tools aren't available, tell the user: "Run /postman:setup to configure the Postman MCP Server."
Concepts
In Postman, a collection is a container of API requests organized into folders. Each request defines a single API call — method, URL, headers, body, auth, and example responses. Collections live in workspaces, which can be personal, team, or public.
Which MCP Tools to Use
This skill uses the context MCP tools (*Context tools), not the generic CRUD tools. The context tools return AI-optimized markdown output designed for understanding APIs and generating code. Always prefer them over the generic equivalents:
What ships with it
2 files 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 · 125 lines · 62 tokens per session scan A 56ef644ea030
postman-context 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 62 tokens to every session and 1,616 once invoked, about $0.0003 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 通用。.
taiyi-diagram-c4
TaiyiForge 辅助 — 从代码反推 C4 架构文档（Observed/Inferred 分层 · Mermaid 真源）。OpenCode / Claude / Codex / Cursor 通用。.
writing-style
Use for technical communication - GitHub/GitLab tickets, PR/MR descriptions, issue comments, code review comments, commit messages. Direct, brief style with no AI-speak. NOT for README.md, public docs, or blog posts.