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 instructions/postman-devrel/postman-claude-code-plugin/claude-mdgit 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.01784 | $0.01784 |
| Opus 5 | $0.00892 | $0.00892 |
| Sonnet 5 | $0.00357 | $0.00357 |
| Haiku 4.5 | $0.00178 | $0.00178 |
Grade A, and why
postman-claude-code-plugin CLAUDE.md 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 — 84 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.
What This Is
The Postman Plugin for Claude Code — a pure-markdown, configuration-driven plugin that provides full API lifecycle management via the Postman MCP Server. No compiled code, no runtime dependencies, no build step.
Repository Structure
.claude-plugin/plugin.json # Plugin manifest (name, version, metadata)
.mcp.json # MCP server auto-config (Postman MCP at mcp.postman.com)
commands/*.md # 15 slash commands (/postman:<name>)
skills/*/SKILL.md # 11 skills (knowledge, agent-ready APIs, CLI, send-request, generate-spec, run-collection, context, and Flows: list-flows, trigger-flow, deploy-flow, get-flow-run)
skills/*/references/*.md # On-demand reference files loaded by skills only when needed
agents/readiness-analyzer.md # Sub-agent for API readiness analysis
examples/ # Sample output (readiness report)
How the Plugin Works
- Claude Code discovers components via
.claude-plugin/plugin.jsonmanifest .mcp.jsonauto-configures the Postman MCP server, providingmcp__postman__*tools. The server mode is switchable viaPOSTMAN_MCP_MODE(mcpfull/default,minimal, orcode— the latter two expose fewer tools;minimallacks the*Contextcode-gen tools)- MCP commands use the cloud Postman MCP Server — authenticate via OAuth in
/postman:setupor aPOSTMAN_API_KEYenvironment variable - Routing is native: there is no routing skill. Claude matches user intent to commands/skills from their front-matter
descriptionfields, so descriptions must state when to use the component - CLI commands use the locally installed Postman CLI (
npm install -g postman-cli) — requirespostman login - Plugin is loaded with
claude --plugin-dir /path/to/postman-claude-code-plugin
Component Conventions
Commands (commands/*.md): YAML front matter with description and allowed-tools. Each defines a structured workflow invoked as /postman:<name>.
- MCP commands: setup, sync, search, test, mock, docs, security, learn (learn requires Full mode —
searchLearningCenteris absent inminimal/code) - CLI commands: request, generate-spec, run-collection, list-flows, trigger-flow, deploy-flow, get-flow-run
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 · 84 lines · 1,784 tokens per session scan A 7fcbd8ca5f64
postman-claude-code-plugin CLAUDE.md is an instructions file published in the GitHub repository Postman-Devrel/postman-claude-code-plugin (38 stars, last pushed 27d ago), licensed Apache-2.0. It adds 1,784 tokens to every session, about $0.0089 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 instructions, from other repositories
claude-code.nvim CLAUDE.md
Instructions for greggh/claude-code.nvim, covering project: claude code plugin, essential commands, project structure, current focus and multi-instance support.
agenthub AGENTS.md
Instructions for nullorder/agenthub, covering agenthub — agent guidelines, what is this project?, project structure, critical rules and plugin json schema.
no-vibe AGENTS.md
Instructions for rizukirr/no-vibe, covering agents, repo purpose, architecture (high-signal files), verification commands and conventions that are easy to miss.
pnCore CLAUDE.md
Claude Code instructions for perniemann/pnCore, covering claude / agent instructions (pncore workspace), frontend aesthetics (global) and pncore resources.
grok-codex-plugin AGENTS.md
AGENTS.md instructions for jinxlzc/grok-codex-plugin: Grok Build plugin that commands the local Codex CLI.
pamplejuce AGENTS.md
Instructions for sudara/pamplejuce, a project described as: A JUCE audio plugin template. JUCE 8, Catch2, Pluginval, macOS notarization, Azure Trusted Signing, Github Actions.