send-request

An HTTP request tool for Postman, a platform for creating and testing API calls. It uses the Postman command-line tool to send requests to web endpoints.

In plain words
What is it for?
Sending GET, POST, or other HTTP requests, testing a specific URL, and checking an API endpoint with its headers, body, or authentication.
Why use it?
It provides a quick way to call an endpoint without opening Postman’s graphical app or writing a temporary script. It also supports requests described in Postman collections.

Skill for Claude CodeCodex

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 skills/postman-devrel/postman-claude-code-plugin/send-request
Any agent
npx skills add Postman-Devrel/postman-claude-code-plugin --skill send-request
Clone the repo
git clone --depth 1 https://github.com/Postman-Devrel/postman-claude-code-plugin

Made for: Claude Code, Codex.

Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,189 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.00035 $0.01189
Opus 5 $0.00017 $0.00594
Sonnet 5 $0.00007 $0.00238
Haiku 4.5 $0.00003 $0.00119

Measured 2d ago against content hash 5506123a352a, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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.

skills/send-request/SKILL.md · 176 lines

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:

  1. List collection folders in postman/collections/
  2. Read the *.request.yaml files to find available requests
  3. Extract method and url from the matching request file
  4. 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>"

Read the full file on GitHub · 176 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. 2d ago First seen · 176 lines · 35 tokens per session scan A 5506123a352a

Subscribe to this mod's changes

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.

Related

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-Devrel/agent-skills · 111 tokens

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?"…

Postman-Devrel/agent-skills · 108 tokens

taiyi-ui-design

TaiyiForge 第 4 阶段 — UI/UX 契约,产出 UI-DESIGN.md。四端通用。.

Dong90/oh-my-taiyiforge · 35 tokens

taiyi-evolve

TaiyiForge 辅助 — 实现后架构与文档同步(architecture-sync)。OpenCode / Claude / Codex / Cursor 通用。.

Dong90/oh-my-taiyiforge · 37 tokens

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…

umputun/cc-thingz · 91 tokens

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.

umputun/cc-thingz · 63 tokens