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 Postman-Devrel/agent-skills --skill postman-api-readinessgit 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-api-readiness)<a href="https://agentmods.dev/skills/postman-devrel/agent-skills/postman-api-readiness"><img src="https://agentmods.dev/badge/skills/postman-devrel/agent-skills/postman-api-readiness/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/postman-devrel/agent-skills/postman-api-readiness"><img src="https://agentmods.dev/badge/skills/postman-devrel/agent-skills/postman-api-readiness.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00108 | $0.02626 |
| Opus 5.5 | $0.00043 | $0.01050 |
| Sonnet 5.5 | $0.00022 | $0.00525 |
| Haiku 4.5 | $0.00011 | $0.00263 |
Grade A, and why
postman-api-readiness 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 1mo 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 — 236 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Readiness Analyzer
Evaluate any API for AI agent compatibility. 48 checks across 8 pillars. Weighted scoring. Actionable fixes.
Version: 2.0.1
Role
You are an opinionated API analyst. You evaluate APIs for AI agent compatibility and don't sugarcoat results. If an API scores 45%, you say so and explain exactly what's broken.
Your job: answer one question. Can an AI agent reliably use this API?
An "agent-ready" API is one that an AI agent can discover, understand, call correctly, and recover from errors without human intervention. Most APIs aren't there yet. You help developers close the gap.
The 8 Pillars
| Pillar | What It Measures | Why Agents Care |
|---|---|---|
| Metadata | operationIds, summaries, descriptions, tags | Agents need to discover and select the right endpoint |
| Errors | Error schemas, codes, messages, retry guidance | Agents need to self-heal when things go wrong |
| Introspection | Parameter types, required fields, enums, examples | Agents need to construct valid requests without guessing |
| Naming | Consistent casing, RESTful paths, HTTP semantics | Agents need predictable patterns to reason about |
| Predictability | Response schemas, pagination, date formats | Agents need to parse responses reliably |
| Documentation | Auth docs, rate limits, external links | Agents need context humans get from reading docs |
| Performance | Rate limit docs, cache headers, bulk endpoints, async | Agents need to operate within constraints |
| Discoverability | OpenAPI version, server URLs, contact info | Agents need to find and connect to the API |
Scoring
Each check has a severity level with weights:
- Critical (4x) - Blocks agent usage entirely
- High (2x) - Causes frequent agent failures
- Medium (1x) - Degrades agent performance
- Low (0.5x) - Nice-to-have improvements
Agent Ready = score of 70% or higher with zero critical failures.
The 48 Checks
What ships with it
1 file 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.
- 1mo ago First seen · 236 lines · 108 tokens per session scan A f557b72fd8b9
postman-api-readiness is a skill published in the GitHub repository Postman-Devrel/agent-skills (17 stars, last pushed 21d ago), licensed MIT. It adds 108 tokens to every session and 2,626 once invoked, about $0.0004 per session on Opus 5.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
flows
Runs, deploys, and debugs Postman Flows from the command line — executing a flow file locally, triggering a deployed flow over its webhook, deploying one so it becomes callable, and tracing a failed run to the block that broke. Use when the user names a flow and an action ("run the Checkout flow", "deploy this flow"…
collection-schema-v3
The reference for the git-native v3 collection file format — one YAML file per request/folder/example under postman/collections/, plus postman/environments/. Read before writing, editing, or generating any file in either directory by hand, or before debugging a collection lint failure. Covers the HTTP…
bootstrap
Resolves the Postman CLI, authenticates, links the workspace, and records this repo's spec path, collections directory and workspace id. Use when the user asks to "set up Postman here", "connect this repo to Postman", "link this workspace", "authenticate with Postman", "postman login", or "run postman init" — and…
api-mocking
Stands up a fake backend that behaves like a real API — from a collection or an OpenAPI spec, running locally or pushed to Postman's cloud for a durable URL — plus request-time scenario and status-code overrides for testing failure paths. Use when the user asks to "mock this API," "create a mock server," "fake the…
api-monitoring
Creates, schedules, and manages Postman Monitors — recurring checks against a live API — triggers ad hoc runs, inspects job/run history to diagnose failures, and hosts self-hosted execution runners for monitors on a private network. Use when the user asks to "set up a monitor," "run this monitor now," "check monitor…
api-discovery
Finds what APIs, collections, specs, or requests already exist before building something new, and answers questions about how they relate. Use when the user asks "does an API for X already exist," "what depends on this service," "what does this API do," or before scaffolding anything that might already have a Postman…