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 commands/logesh-works/postman-mcp/indexgit clone --depth 1 https://github.com/logesh-works/postman-mcpWrote 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/commands/logesh-works/postman-mcp/index)<a href="https://agentmods.dev/commands/logesh-works/postman-mcp/index"><img src="https://agentmods.dev/badge/commands/logesh-works/postman-mcp/index.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.00000 | $0.00771 |
| Opus 5 | $0.00000 | $0.00385 |
| Sonnet 5 | $0.00000 | $0.00154 |
| Haiku 4.5 | $0.00000 | $0.00077 |
Grade A, and why
index 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.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Commands
After postman-mcp init, seven slash commands are
available inside Claude Code. The sync commands aren't separate implementations: they all
go through the same validate → verify → diff → confirm → write pipeline, and differ only
in which routes Claude analyzes and where the result lands.
| Command | One-liner |
|---|---|
/postman:syncapi |
Sync one route. The kernel that everything else is built on. |
/postman:syncchanges |
Sync what changed since the last sync. The one you'll run most. |
/postman:sync |
Sync everything in one file, module, or directory. |
/postman:syncall |
Sync the whole codebase. Usually a first-run or post-refactor thing. |
/postman:prompt |
Sync from a plain-English instruction (add error responses, headers, etc.). |
/postman:createenv |
Generate a Postman environment from your code. |
/postman:status |
Show drift without writing anything. |
The diff-then-confirm contract
Every write-capable command follows the same two-phase contract, so nothing reaches Postman as a surprise:
sequenceDiagram
participant You
participant CC as Claude Code
participant S as MCP server
participant P as Postman
You->>CC: /postman:syncapi create_payment
Note over CC: Claude reads the code and authors<br/>collection.json + metadata.json
CC->>S: sync_files(confirm=false)
S->>P: GET collection (read structure)
S-->>CC: validated, verified diff preview (writes nothing)
CC-->>You: diff ... Write to Postman? [y/n]
You->>CC: y
CC->>S: sync_files(confirm=true)
S->>P: PUT merged collection
S-->>CC: written
On n, nothing is written. There's no flag to skip this step; see the
safety rules. Once the result is shown (either the
write confirmation or the n abort), the command ends. Claude doesn't keep going with
more analysis or commentary after that.
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 · 66 lines · 0 tokens per session scan A 0c12192f11a0
index is a command published in the GitHub repository logesh-works/postman-mcp (1 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 771 tokens. 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.