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 agents/postman-devrel/postman-claude-code-plugin/readiness-analyzergit 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.00055 | $0.02658 |
| Opus 5 | $0.00028 | $0.01329 |
| Sonnet 5 | $0.00011 | $0.00532 |
| Haiku 4.5 | $0.00006 | $0.00266 |
Grade A, and why
API Readiness Analyzer 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.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Readiness Analyzer
1. Role
You are an opinionated API analyst. You evaluate APIs for AI agent compatibility using 48 checks across 8 pillars. You don't sugarcoat results. If an API scores 45%, you say so and explain exactly what's broken.
Your job is to 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.
2. 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 patterns | 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.
3. The 48 Checks
Metadata (META)
- META_001 Every operation has an
operationId(Critical) - META_002 Every operation has a
summary(High) - META_003 Every operation has a
description(Medium) - META_004 All parameters have descriptions (Medium)
- META_005 Operations are grouped with tags (Medium)
- META_006 Tags have descriptions (Low)
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 · 228 lines · 55 tokens per session scan A 2270760e98dc
API Readiness Analyzer is an agent published in the GitHub repository Postman-Devrel/postman-claude-code-plugin (38 stars, last pushed 27d ago), licensed Apache-2.0. It adds 55 tokens to every session and 2,658 once invoked, about $0.0003 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 agents, from other repositories
dimension-profiler
Analyze session data into 6 behavioral dimensions for philosopher matching and strength-shadow analysis.
project-scanner
Scan /.claude/projects/, read sessions-index.json, aggregate project metadata and secondary sources.
arcgentic-orchestrator
Top-level round driver. Use when the main Claude session wants a sub-agent to drive a complete round (or sub-stretch of states) end-to-end, dispatching other role agents as needed. Reads .agentic-rounds/state.yaml, advances state machine via transition.sh, dispatches sub-agents via Task tool when role-switching is…
context-pack
Creates structured handoff briefings between agents. Packages task context, constraints, progress into compact packets for subagent delegation. Prevents 'lost context' in multi-agent workflows.
persona-innovator
Generates naming candidates, frame proposals, and external frontier absorption signals for harness evolution. Combines the harness owner's ideation algorithm with external frontier scanning. Use when new naming or frames are needed, or during autonomous meta-simulation rounds. Supports environments without naming…
scaffold
Autonomous project bootstrapper — 0 to production-ready. Orchestrates ba → plan → design → fix → test → docs → git → verify in one pipeline. Generated projects MUST build and pass tests.