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/agent-skills/postmannpx skills add Postman-Devrel/agent-skills --skill postmangit clone --depth 1 https://github.com/Postman-Devrel/agent-skillsWrote 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/agent-skills/postman)<a href="https://agentmods.dev/skills/postman-devrel/agent-skills/postman"><img src="https://agentmods.dev/badge/skills/postman-devrel/agent-skills/postman.svg" alt="Measured on agentmods" 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 | $0.00111 | $0.05232 |
| Opus 5 | $0.00056 | $0.02616 |
| Sonnet 5 | $0.00022 | $0.01046 |
| Haiku 4.5 | $0.00011 | $0.00523 |
Grade A, and why
postman scanned grade A with 2 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 3d 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.
Sends data to an external URLlowData exfiltration
A POST to an outside endpoint may be telemetry or may be exfiltration; either way the mod talks to somewhere, and you should know where.
curl -X POST https://<mock-id>.mock.pstmn.io/pets -d '{"name":"Buddy"}' Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl https://<mock-id>.mock.pstmn.io/pets How it starts
The opening of the file, as written. The whole thing — 567 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Postman Agent Skill
Full API lifecycle management through the Postman MCP Server. Sync specs, generate code, run tests, create mocks, publish docs, and audit security.
Version: 2.0.1 Requires: Postman MCP Server
Prerequisites
This skill requires the Postman MCP Server to be configured. The MCP server exposes 111+ tools for interacting with Postman workspaces, collections, specs, environments, mocks, monitors, and more.
Setup check: Call getAuthenticatedUser via MCP. If it succeeds, you're connected. If it fails, walk through Setup below.
Important: MCP Tool Behavior
Before using the workflows below, be aware of these behaviors:
getWorkspacesreturns ALL workspaces. For large organizations this can be 300KB+. If you already have a workspace ID, usegetWorkspace(workspaceId)directly instead.getCollectiondefault response is a lightweight map withitemRefs(folder/request tree). This is efficient for discovery. Only usemodel=fullwhen you need complete request/response bodies, and be aware it can exceed 300KB for large collections. Prefer targetedgetCollectionRequestandgetCollectionResponsecalls for specific endpoints.getTaggedEntitiesreturns 404 for missing tags, not an empty array. Handle this gracefully. Tag functionality may require an Enterprise plan.runCollectionreturns aggregate results only (total requests, passed, failed, duration). It does NOT return per-request detail or error messages. For debugging specific failures, examine individual requests withgetCollectionRequestandgetCollectionResponseafter the run.searchPostmanElementsonly searches the PUBLIC Postman network, not private workspaces. Always search private workspace first withgetCollections.
Setup
If MCP tools are not available or getAuthenticatedUser fails:
- Get a Postman API key:
- Go to https://postman.postman.co/settings/me/api-keys
- Click "Generate API Key", name it "Claude Code"
- Copy the key (starts with PMAK-)
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.
- 3d ago First seen · 567 lines · 111 tokens per session scan A 2442d98f539e
postman is a skill published in the GitHub repository Postman-Devrel/agent-skills (16 stars, last pushed 5mo ago), licensed MIT. It adds 111 tokens to every session and 5,232 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 2 findings (sends data to an external url, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
generate-spec
Generate or update an OpenAPI 3.0 spec from code. Use when the user wants to create, update, or write an OpenAPI/Swagger spec, API definition, or API documentation from their codebase.
run-collection
Run Postman collection tests using the Postman CLI. Use when the user wants to run collection tests, execute API test suites, or verify changes after editing code.
send-request
Send HTTP requests using the Postman CLI. Use when the user wants to send a request, call or test an HTTP endpoint, or quickly try an API.
trigger-flow
Trigger (run) a deployed Postman Flow via the Postman CLI with natural-language inputs. Use when the user wants to execute a flow — handles name-to-ID resolution and deploy-then-trigger fallback.
deploy-flow
Deploy a Postman Flow so it becomes triggerable, using the Postman CLI. Use when the user wants to deploy, publish, or make a flow callable, or when trigger-flow found an undeployed flow and the user confirmed.
postman-cli
Postman CLI reference and git sync file structure knowledge - provides context for CLI-based commands (send-request, generate-spec, run-collection, context).