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 skills add LambdaTest/agent-skills --skill postman-collection-generatorgit clone --depth 1 https://github.com/LambdaTest/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/lambdatest/agent-skills/postman-collection-generator)<a href="https://agentmods.dev/skills/lambdatest/agent-skills/postman-collection-generator"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/postman-collection-generator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/lambdatest/agent-skills/postman-collection-generator"><img src="https://agentmods.dev/badge/skills/lambdatest/agent-skills/postman-collection-generator.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00139 | $0.01381 |
| Opus 5 | $0.00069 | $0.00691 |
| Sonnet 5 | $0.00028 | $0.00276 |
| Haiku 4.5 | $0.00014 | $0.00138 |
Grade A, and why
postman-collection-generator 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 11d 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 — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Postman Collection Generator
Generates a valid, import-ready Postman Collection v2.1 JSON from:
- Natural language API descriptions
- cURL commands (one or many)
- Mixed input (some endpoints described, some as cURL)
Step 1 — Extract API Information
Parse the user's input and extract for each endpoint:
| Field | Source |
|---|---|
| Name | Described name or inferred from path |
| Method | Explicit or inferred (GET for fetches, POST for creates, etc.) |
| URL | Full URL or path; use {{base_url}} variable for the host |
| Headers | From cURL -H flags or described headers |
| Auth | Bearer token, Basic, API Key, or None |
| Body | From cURL -d / --data or described payload (JSON, form-data) |
| Query params | From URL ?key=value or described filters |
If input is ambiguous, make reasonable REST conventions and note assumptions at the end.
Step 2 — Build the Collection JSON
Use this exact v2.1 structure:
{
"info": {
"name": "<Collection Name>",
"schema": "https://schema.getpostman.com/json/collection/v2.1.0/collection.json",
"_postman_id": "<generate a UUID v4>",
"description": "<brief description>"
},
"variable": [
{ "key": "base_url", "value": "<extracted base URL or placeholder>", "type": "string" }
],
"auth": <collection-level auth if shared across requests, else null>,
"item": [ <request items or folders> ]
}
Request item structure:
{
"name": "Get Users",
"request": {
"method": "GET",
"header": [
{ "key": "Content-Type", "value": "application/json" }
],
"url": {
"raw": "{{base_url}}/users",
"host": ["{{base_url}}"],
"path": ["users"],
"query": []
},
"body": null,
"auth": null,
"description": ""
},
"response": []
}
Body (when present):
"body": {
"mode": "raw",
"raw": "{\n \"key\": \"value\"\n}",
"options": { "raw": { "language": "json" } }
}
Grouping:
- Group related endpoints into folders using the
itemarray nested inside an item with"name"but no"request"key. - Use logical grouping: by resource (Users, Orders) or by feature.
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.
- 11d ago First seen · 182 lines · 139 tokens per session scan A 30825fe0aa9a
postman-collection-generator is a skill published in the GitHub repository LambdaTest/agent-skills (366 stars, last pushed 1mo ago), licensed MIT. It adds 139 tokens to every session and 1,381 once invoked, about $0.0007 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
detecting-broken-object-property-level-authorization
Detect and test for OWASP API3:2023 Broken Object Property Level Authorization vulnerabilities including excessive data exposure and mass assignment attacks.
API Test Suite Generator
Automatically generate comprehensive API test suites from OpenAPI specifications covering CRUD operations, error handling, authentication, pagination, and edge cases.
flowforge-testing
Generate, modify, validate, execute and triage Flow Forge API test cases. Use when the user wants to turn requirement documents, API documents, table structures or business rules into executable YAML/Excel test cases, revise existing cases after requirement/API changes, run cases with the Flow Forge executor and…
kahea
Safely use HTTP APIs and finite WebSocket sessions through the Kāhea deterministic invocation kernel. Use when an agent must discover operations from OpenAPI, Postman, HAR, cURL, HTTP files, direct descriptors, websocket-session JSON/YAML, or the supported AsyncAPI 2.6/3.0 WebSocket subset; create and review sealed…
bruno
Comprehensive operational skill specification for Anthropic Claude to automate, script, troubleshoot, and optimize Bruno API Client, Bru markup language (.bru), CLI runner (@usebruno/cli), and CI/CD test pipelines.
api-spec-generator
Generate a ready-to-import Postman or Bruno collection from an API spec, Swagger/OpenAPI file, or endpoint description. Use this skill whenever the user wants to create, export, or scaffold an API test collection. Triggers on: "generate Postman collection", "create Bruno spec", "import-ready collection", "generate…