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/agent-ready-apisnpx skills add Postman-Devrel/postman-claude-code-plugin --skill agent-ready-apisgit clone --depth 1 https://github.com/Postman-Devrel/postman-claude-code-pluginWrote 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/postman-claude-code-plugin/agent-ready-apis)<a href="https://agentmods.dev/skills/postman-devrel/postman-claude-code-plugin/agent-ready-apis"><img src="https://agentmods.dev/badge/skills/postman-devrel/postman-claude-code-plugin/agent-ready-apis.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.00471 |
| Opus 5 | $0.00016 | $0.00235 |
| Sonnet 5 | $0.00007 | $0.00094 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
agent-ready-apis 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 4d 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
Agent-Ready APIs
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.
When to Suggest the Analyzer
If the user mentions any of these, suggest running the readiness-analyzer agent:
- "Is my API agent-ready?"
- "Can AI agents use my API?"
- "Scan my API" / "Analyze my spec"
- "What's wrong with my API for AI?"
- "How agent-friendly is my API?"
- "Improve my API for AI agents"
What Gets Evaluated
The analyzer checks 48 items across 8 pillars:
| Pillar | What It Measures |
|---|---|
| Metadata | operationIds, summaries, descriptions, tags |
| Errors | Error schemas, codes, messages, retry guidance |
| Introspection | Parameter types, required fields, enums, examples |
| Naming | Consistent casing, RESTful paths, HTTP semantics |
| Predictability | Response schemas, pagination, date formats |
| Documentation | Auth docs, rate limits, external links |
| Performance | Rate limit headers, cache, bulk endpoints, async patterns |
| Discoverability | OpenAPI version, server URLs, contact info |
Scoring
- Critical checks (4x weight): Blocks agent usage entirely
- High checks (2x weight): Causes frequent agent failures
- Medium checks (1x weight): Degrades agent performance
- Low checks (0.5x weight): Nice-to-have improvements
Agent Ready = score of 70% or higher with zero critical failures.
Interpreting Results
- 90-100%: Excellent. Agents can use this API reliably.
- 70-89%: Agent-ready. Minor improvements possible.
- 50-69%: Not agent-ready. Key issues need fixing.
- Below 50%: Significant work needed. Focus on critical failures first.
See pillars.md in this skill folder for the full check reference.
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.
- 4d ago First seen · 53 lines · 33 tokens per session scan A 8bd4106cba0c
agent-ready-apis is a skill published in the GitHub repository Postman-Devrel/postman-claude-code-plugin (40 stars, last pushed 29d ago), licensed Apache-2.0. It adds 33 tokens to every session and 471 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 通用。.
taiyi-diagram-c4
TaiyiForge 辅助 — 从代码反推 C4 架构文档（Observed/Inferred 分层 · Mermaid 真源）。OpenCode / Claude / Codex / Cursor 通用。.
flow-next-resolve-pr
Resolve PR review feedback. Fetches unresolved threads, triages, fixes, replies and resolves via GraphQL. Use when asked to address review comments.