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/statusgit 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/status)<a href="https://agentmods.dev/commands/logesh-works/postman-mcp/status"><img src="https://agentmods.dev/badge/commands/logesh-works/postman-mcp/status.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.00362 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
status 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 3d 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.
What it actually says
/postman:status: drift check (read-only)
Shows what would sync: new, modified, and deprecated routes, plus anything in the
collection that has drifted from the code, without writing anything. It's
syncall's diff minus the write.
Usage
/postman:status [--since commit|date|last]
| Flag | Effect |
|---|---|
| (none) | Compare the whole codebase against the live collection. |
--since <commit|date> |
Limit the check to changes since a ref. |
--since last |
Check changes since the last sync marker. |
When to use it
- Before a release, to check whether the collection is in sync.
- In a code review, to see the API surface a PR actually changes.
- Any time you want a drift report with zero risk of accidentally writing something.
Example
/postman:status
Collection: Acme Backend
Plan: 1 new · 1 modified
[NEW] POST /payments/refund → (root) ✓ verified (app/payments.py:58)
[MODIFY] GET /orders/{id} → (root) ✓ verified (app/orders.py:40)
Write to Postman? Re-run with confirm=true to apply.
status calls the same discovery and verification path as every sync command, but the
turn ends after showing this preview — it never calls the tool again with confirm: true.
Since it never writes, it's safe to run as often as you like. It's also the basis for the
CI drift-gate planned down the line.
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.
- 3d ago First seen · 43 lines · 0 tokens per session scan A 3685c7f3b96d
status 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 362 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.
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.