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/syncchangesgit 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.00637 |
| Opus 5 | $0.00000 | $0.00318 |
| Sonnet 5 | $0.00000 | $0.00127 |
| Haiku 4.5 | $0.00000 | $0.00064 |
Grade A, and why
syncchanges 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/postman:syncchanges: sync what changed
This is the one you'll run most. After you write code and commit, it syncs only what changed, and you never have to think about git refs to use it.
Usage
/postman:syncchanges [--last N] [--since commit|date]
For free-form instructions (add error responses, headers, a rewritten description, …),
use /postman:prompt instead.
Default behavior
With no flags, it syncs everything changed since lastUpdate.commit, the marker written
by your last sync. You never name a git ref yourself.
| Flag | Effect |
|---|---|
| (none) | Everything changed since the last sync. |
--last 3 |
The last 3 commits. No need to remember HEAD~3 syntax. |
--since 2026-06-01 |
Everything since a date. |
--since a1b2c3d |
Everything since a specific commit. |
!!! warning "First run with no marker"
If there's no lastUpdate.commit yet, the command errors gently and suggests
/postman:syncall for the initial full sync.
How each change is handled
| Change type | Behavior |
|---|---|
| New route | Full create. |
| Modified route | Only the changed structural fields are updated; human-owned scripts and examples are preserved. |
| Deleted route | Noted in the sync notes, not auto-removed or deprecated yet — deletion handling is still manual. Remove the stale request from the collection by hand. |
Why it's cheap
syncchanges parses only the files that changed since the last marker, not the whole
project, and reads just the collection's basic structure rather than mirroring it
locally. That's what keeps token usage low enough to run after every change instead of
saving it up.
Example
<edit routes/payments.py, commit>
/postman:syncchanges
Collection: Acme Backend
Plan: 1 new · 1 modified
[MODIFY] POST /payments → (root) ✓ verified (routes/payments.py:12)
[NEW] GET /payments/{id} → (root) ✓ verified (routes/payments.py:24)
Write to Postman? Re-run with confirm=true to apply.
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 · 71 lines · 0 tokens per session scan A 710e7456f149
syncchanges 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 637 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.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
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.