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/syncgit clone --depth 1 https://github.com/logesh-works/postman-mcpWhat 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.00519 |
| Opus 5 | $0.00000 | $0.00260 |
| Sonnet 5 | $0.00000 | $0.00104 |
| Haiku 4.5 | $0.00000 | $0.00052 |
Grade A, and why
sync 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 yesterday.
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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/postman:sync: file, module, or directory
Syncs every route in one file, module, or directory. Broader than a single route, narrower than the whole codebase.
Usage
/postman:sync -<filename|module|directory> [--into path]
For free-form instructions (add error responses, headers, a rewritten description, …),
use /postman:prompt instead.
Targeting
The target after - is fuzzy-matched against your project:
- A file, like
-routes/payments.py - A module, like
-app.api.payments - A directory, like
-routes/
If the target is ambiguous, the command lists the candidates and asks you to be specific. It never guesses.
Flags
| Flag | Effect |
|---|---|
--into <path> |
Folder inside the collection where the requests land. Missing folders are created automatically. If omitted, falls back to config.defaultInto, which defaults to the collection root. No folder gets inferred from the file or module name. |
Example
/postman:sync -routes/payments.py --into payments
Collection: Acme Backend
Plan: 2 new · 1 modified
[NEW] POST /payments → payments ✓ verified (routes/payments.py:12)
[NEW] GET /payments/{id} → payments ✓ verified (routes/payments.py:24)
[MODIFY] DELETE /payments/{id} → payments ✓ verified (routes/payments.py:31)
Write to Postman? Re-run with confirm=true to apply.
Each request is matched against the live collection by METHOD + normalized path, so
re-running this updates routes in place instead of creating duplicates. See
idempotency. Once the write result is
shown, the command ends; no further analysis or follow-on commentary.
Free-form instructions
sync itself is plain and deterministic. For anything free-form (add error responses,
headers, a rewritten description, example values), use
/postman:prompt "<text>" — Claude targets this same file/module/dir sync
under the hood and applies the changes through the same diff-then-confirm gate. See the
Prompt & skill layer.
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.
- yesterday First seen · 59 lines · 0 tokens per session scan A 4efd97019b19
sync 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 519 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
git
Git operations with intelligent commit messages and workflow optimization.
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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.