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 skills add Aryan-Jhaveri/mcp-statcan --skill postman-mcp-servergit clone --depth 1 https://github.com/Aryan-Jhaveri/mcp-statcanWrote 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/skills/aryan-jhaveri/mcp-statcan/postman-mcp-server)<a href="https://agentmods.dev/skills/aryan-jhaveri/mcp-statcan/postman-mcp-server"><img src="https://agentmods.dev/badge/skills/aryan-jhaveri/mcp-statcan/postman-mcp-server/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/aryan-jhaveri/mcp-statcan/postman-mcp-server"><img src="https://agentmods.dev/badge/skills/aryan-jhaveri/mcp-statcan/postman-mcp-server.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00063 | $0.00815 |
| Opus 5.5 | $0.00025 | $0.00326 |
| Sonnet 5.5 | $0.00013 | $0.00163 |
| Haiku 4.5 | $0.00006 | $0.00081 |
Grade A, and why
postman-mcp-server 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 today.
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.
Postman MCP Server
MCP exposes workspace resources directly to an agent. Existing collections, specs, examples, and environments provide maintained API knowledge; fetching the relevant entity preserves that context when a local CLI workflow is not available. For repository edits and Git review, prefer the local workflows in api-engineer and bootstrap when available.
Each tool definition exposed to the model consumes context whenever it is
included in a request. Prefer the smallest available toolset that covers the
task; expanding to every tool can crowd out the API evidence needed to reason.
When exposed, call getEnabledTools to inspect the active toolset before
diagnosing a missing operation. Otherwise use the host's discovered tools and
report that limitation. Do not infer availability from reference tool names or
assume a client can switch a route pinned to a specific MCP endpoint.
- Select tools from the connected server's actual surface. Tool availability varies by mode; a name listed in a reference is not proof it is exposed. Use setup for connection/auth failures and limitations when an operation is missing or behaves differently from the CLI.
- Search to locate an entity, then fetch enough detail to work on it.
searchPostmanElementsfinds candidates; collection, spec, and workspace detail tools establish IDs, ownership, and content. A search preview is insufficient evidence for replacing a collection or declaring an API absent. - Match the mutation to the intended scope. Request-level updates preserve unrelated collection content; whole-collection replacement requires the current complete object. A workspace is a container and access boundary, not a reason to create duplicate resources whenever a new task begins.
- Preserve the source of truth when synchronizing. Spec-to-collection generation reuses the interface, while collection-to-spec sync carries changes in the other direction. Choose from the intended contract rather than overwriting whichever artifact is easiest to reach. An asynchronous acceptance response needs a completed task result before claiming sync.
- Treat publication separately from editing. A collection example can feed docs and a classic mock, but neither becomes publicly accessible merely because it exists. Apply the user's intended audience and authorization before publishing docs or mocks, or changing shared resources.
Read the reference for the branch being used:
| Task | Reference and decision it supports |
|---|---|
| Locate an API | Search: narrow candidates to the intended resource |
| Generate or synchronize artifacts | Sync: choose source and track completion |
| Serve saved examples | Mock: classic collection mocks; for CLI Code Mocks use api-mocking |
| Execute saved assertions | Test: distinguish run completion from failures |
| Improve or publish docs | Docs: fill contract gaps and verify reader access |
| Requested security review | Security: assess concrete API risks |
| Product how-to questions | Learning Center: product documentation search when exposed |
What ships with it
9 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 66 lines · 63 tokens per session scan A 2e306eb4bd70
postman-mcp-server is a skill published in the GitHub repository Aryan-Jhaveri/mcp-statcan (7 stars, last pushed yesterday), licensed MIT. It adds 63 tokens to every session and 815 once invoked, about $0.0003 per session on Opus 5.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-10-27.
Other skills, from other repositories
test-driven-development
Use when implementing any feature or bugfix, before writing implementation code.
playwright-cli
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
idpsim
Test enterprise sign-on locally with idpsim, haven's identity-provider stand-in: OIDC, SAML, SCIM provisioning and domain verification with no external IdP account. Use when someone says 'haven idp', 'idpsim', 'fake IdP', 'test SSO locally', 'SAML login', 'OIDC provider', 'SCIM push', 'provision users', 'domain…