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/send-requestnpx skills add Postman-Devrel/postman-claude-code-plugin --skill send-requestgit 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.00035 | $0.01189 |
| Opus 5 | $0.00017 | $0.00594 |
| Sonnet 5 | $0.00007 | $0.00238 |
| Haiku 4.5 | $0.00003 | $0.00119 |
Grade A, and why
send-request 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an API testing assistant that helps send HTTP requests using the Postman CLI.
When to Use This Skill
Trigger this skill when:
- User asks to "send a request" or "make a request"
- User wants to "test an endpoint" or "hit the API"
- User says "call the API" or "try the endpoint"
- User wants to verify an endpoint is working
- User asks to test a specific URL
Step 1: Determine Request Details
If user provides a URL directly:
- Extract method (default to GET if not specified)
- Extract URL
- Note any headers, body, or auth mentioned
If user wants to send a request from a collection:
Collections use the v3 folder format — each collection is a directory containing *.request.yaml files:
postman/collections/
├── My API/
│ ├── .resources/
│ │ └── definition.yaml # schemaVersion: "3.0", name
│ ├── Get Users.request.yaml # method: GET, url: https://...
│ ├── Create User.request.yaml
│ └── Auth/
│ └── Login.request.yaml
Each *.request.yaml contains:
$kind: http-request
url: https://api.example.com/users
method: GET
order: 1000
To find requests from collections:
- List collection folders in
postman/collections/ - Read the
*.request.yamlfiles to find available requests - Extract
methodandurlfrom the matching request file - Ask user which request to send (if multiple match)
Step 2: Build the Command
Basic request:
postman request <METHOD> "<URL>"
With headers (repeatable):
postman request <METHOD> "<URL>" \
-H "Header-Name: value" \
-H "Another-Header: value"
With body (POST/PUT/PATCH):
# Inline JSON
postman request <METHOD> "<URL>" -d '{"key": "value"}'
# From file
postman request <METHOD> "<URL>" -d @body.json
With form data (repeatable, supports file upload):
postman request <METHOD> "<URL>" \
-f "field=value" \
-f "file=@path/to/file.png"
With authentication:
# Bearer token
postman request <METHOD> "<URL>" --auth-bearer-token "<token>"
# API Key
postman request <METHOD> "<URL>" --auth-apikey-key "X-API-Key" --auth-apikey-value "<key>"
# Basic auth
postman request <METHOD> "<URL>" --auth-basic-username "<user>" --auth-basic-password "<pass>"
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 · 176 lines · 35 tokens per session scan A 5506123a352a
send-request 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 35 tokens to every session and 1,189 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.