generate-spec

A command that creates or updates an OpenAPI 3.0 specification, a standard description of an API's routes, inputs, outputs, and security rules, by examining the codebase.

In plain words
What is it for?
Use it to find routes in common programming frameworks and produce a YAML specification containing endpoints, parameters, request bodies, responses, models, and authentication details.
Why use it?
It removes the need to document every endpoint by hand and helps keep API documentation aligned with the implementation.

Command

Install

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.

agentmods
npx agentmods add commands/postman-devrel/postman-claude-code-plugin/generate-spec
Clone the repo
git clone --depth 1 https://github.com/Postman-Devrel/postman-claude-code-plugin
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 470 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00470
Opus 5 $0.00005 $0.00235
Sonnet 5 $0.00002 $0.00094
Haiku 4.5 $0.00001 $0.00047

Measured 2d ago against content hash 9e0ba9ed27f1, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

generate-spec 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.

commands/generate-spec.md · 56 lines

What it actually says

Generate or update an OpenAPI 3.0 specification by analyzing API routes in your codebase.

Step 1: Check for Existing Spec

ls postman/specs/**/*.yaml postman/specs/**/*.yml postman/specs/**/*.json 2>/dev/null
ls openapi.yaml openapi.yml swagger.yaml swagger.yml 2>/dev/null

If a spec exists, read it to understand current state. You'll update it rather than replace it.

Step 2: Discover API Endpoints

Scan the project for route definitions based on the framework:

  • Express/Node: app.get(), router.post(), @Get() (NestJS)
  • Python: @app.route(), @router.get() (FastAPI), path() (Django)
  • Go: http.HandleFunc(), r.GET() (Gin/Echo)
  • Java: @GetMapping, @PostMapping, @RequestMapping
  • Ruby: get, post, resources in routes.rb

Read the route files and extract: methods, paths, parameters, request bodies, response schemas, auth requirements.

Step 3: Generate or Update the Spec

Write a valid OpenAPI 3.0.3 YAML spec including:

  • info with title, version, description
  • servers with local dev URL
  • paths with all discovered endpoints
  • components/schemas with models derived from code (types, models, structs)
  • components/securitySchemes if auth is used

When updating: Add new endpoints, update changed ones, remove endpoints no longer in code. Preserve existing descriptions and examples.

When creating: Write to postman/specs/openapi.yaml.

Step 4: Validate

postman spec lint ./postman/specs/openapi.yaml

Fix any validation errors and re-run until clean.

Step 5: Report

Show what was created or changed:

  • Endpoints documented (count and list)
  • Schemas defined
  • Changes from previous spec (if updating)
  • Validation result
Changes

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.

  1. 2d ago First seen · 56 lines · 11 tokens per session scan A 9e0ba9ed27f1

Subscribe to this mod's changes

generate-spec 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 11 tokens to every session and 470 once invoked, about $0.0001 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.

Related

Other commands, from other repositories