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 commands/postman-devrel/postman-claude-code-plugin/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.00007 | $0.00303 |
| Opus 5 | $0.00003 | $0.00151 |
| Sonnet 5 | $0.00001 | $0.00061 |
| Haiku 4.5 | $0.00001 | $0.00030 |
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.
What it actually says
Send an HTTP request using the Postman CLI. Ask the user what URL and method they want, or detect it from context.
Step 1: Determine Request Details
Ask the user for:
- URL to send the request to
- HTTP method (default: GET)
- Any headers, body, or auth needed
If the user wants to send a request from a collection, find collection folders in postman/collections/ and read the *.request.yaml files to extract method and URL. Collections use the v3 folder format.
Step 2: Build and Execute
postman request <METHOD> "<URL>"
With headers: add -H "Header: value"
With body: add -d '{"key": "value"}'
With bearer auth: add --auth-bearer-token "<token>"
With API key: add --auth-apikey-key "<name>" --auth-apikey-value "<key>"
With basic auth: add --auth-basic-username "<user>" --auth-basic-password "<pass>"
With environment: add -e ./postman/environments/<file>.json
Always show the exact command before running it.
Step 3: Report Results
Parse the response and report status code, response time, and body. Suggest fixes for errors (auth issues, connection problems, invalid URLs).
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 · 34 lines · 7 tokens per session scan A 7b6be3576211
send-request is a command published in the GitHub repository Postman-Devrel/postman-claude-code-plugin (38 stars, last pushed 27d ago), licensed Apache-2.0. It adds 7 tokens to every session and 303 once invoked, about $0.0000 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 commands, from other repositories
refine-title
深度分析 Issue 或 PR 内容，并将其标题重构为 Conventional Commits 格式.
warden-cost
Dollar accounting — what does each active rule actually save, in money? Translates the token-measured verdict into dollars using a price table and the agent's own token-type mix, with a per-session net and a break-even. Read-only; spends no tokens.
routine
Execute one maintenance routine defined in scv/routines/ .md (task + guardrails + exit-criteria contract), or list defined routines. SCV never schedules — pair with host features like /loop or cron yourself. Use whenever the user asks to run a recurring maintenance task, or asks what routines exist — not only when…
incident
Live incident response — intake a Sentry issue, stack trace, or symptom; gate mitigate-first vs root-cause-first; keep a UTC timeline. Use when production is broken RIGHT NOW; for the after-action write-up alone, use /orc:postmortem.
t800-onboard
Для чата с новичками. Показывает, что настроено в Cursor (global + local), и что умеет отдел T-800.
t800-bootstrap
Запускайте один раз при установке плагина или для новичка в чате.