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 api-documentationgit 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/api-documentation)<a href="https://agentmods.dev/skills/aryan-jhaveri/mcp-statcan/api-documentation"><img src="https://agentmods.dev/badge/skills/aryan-jhaveri/mcp-statcan/api-documentation/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/api-documentation"><img src="https://agentmods.dev/badge/skills/aryan-jhaveri/mcp-statcan/api-documentation.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.00061 | $0.00558 |
| Opus 5.5 | $0.00024 | $0.00223 |
| Sonnet 5.5 | $0.00012 | $0.00112 |
| Haiku 4.5 | $0.00006 | $0.00056 |
Grade A, and why
api-documentation 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 — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Documentation
A maintained contract gives callers enough information to integrate without reading the implementation. Keeping descriptions and examples beside the API artifacts lets the same knowledge support documentation, tests, and mocks, with changes reviewable alongside code.
- Start from the existing source of truth. An OpenAPI spec describes the interface for tooling; a Postman collection adds runnable requests, examples, and assertions. Maintain both when both uses matter, with an explicit direction of generation or synchronization so they do not become competing definitions. Local edits need bootstrap only when setup or bindings are unresolved.
- When the spec is authoritative, reuse its operations with
postman spec generate collection <spec-path-or-id> -n "<collection-name>". Inspect the generated result before replacing an existing collection: maintained scripts and examples carry knowledge beyond endpoint shapes. - Describe what changes a caller's decision: required versus optional inputs, auth and scopes, response guarantees, pagination, retryable failures, and side effects. Derive guarantees from the agreed contract or verified behavior; label unresolved design choices instead of inventing them. Use REST design guidance when a design choice affects usability or compatibility, not to redesign an unrelated interface while filling a documentation gap.
- Save examples that clarify consequential cases, including relevant errors. Examples become inputs for mocks as well as explanations for readers; a success-only example can hide the failure path callers must handle. Use collection-schema-v3 for local collection edits and variables to keep credentials out of reusable requests and examples.
- Choose delivery by audience. Local artifacts support Git review; publishing to the bound workspace makes them available to teammates with access (see bootstrap). A workspace push does not itself publish a public docs page or change permissions. For a public documentation link, use postman-mcp-server's documentation workflow and the available publishing tool; establish the intended audience before public exposure.
What ships with it
1 file 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 · 48 lines · 61 tokens per session scan A 4f01faa4a8b4
api-documentation is a skill published in the GitHub repository Aryan-Jhaveri/mcp-statcan (7 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 558 once invoked, about $0.0002 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
phone
Use when the user wants phone-number intelligence (lookup, carrier, line type, SIM-swap / call-forwarding fraud signals), US/CA number provisioning (rent a phone number), or outbound AI voice calls (Bland.ai under the hood — schedule, confirm, follow-up). Pay per call in USDC.
bi-causal-attribution
A business-analysis skill that links business events in reports, plans, release notes, or conversations with an unusual metric change. It produces and ranks possible causes supported by the available evidence.
nornweave-api
Give AI agents their own email inboxes using the NornWeave API. Use when building email agents, sending/receiving emails programmatically, managing inboxes, retrieving threads, searching messages, or integrating with email providers (Mailgun, SES, SendGrid, Resend). NornWeave provides LLM-ready markdown parsing and…
flowllm-dev
FlowLLM repository development guidance. Use when working in the flowllm codebase to implement, debug, test, review, or document FlowLLM runtime behavior, including CLI/client calls, services, application wiring, jobs, steps, components, configuration, streaming, registry registration, and tests.
scraperapi-java-sdk
Best-practices reference for the ScraperAPI Java SDK (com.scraperapi:sdk Maven artifact). Consult whenever the user is writing, debugging, or reviewing Java code that calls ScraperAPI. Use when user asks: "scrape a website with Java and ScraperAPI", "ScraperAPI Java example", "how do I add ScraperAPI to my Maven…
scraperapi-php-sdk
Best-practices reference for the ScraperAPI PHP SDK (scraperapi/sdk Composer package). Consult whenever the user is writing, debugging, or reviewing PHP code that calls ScraperAPI. Use when user asks: "scrape a website with PHP and ScraperAPI", "ScraperAPI PHP example", "how do I use the ScraperAPI PHP SDK", "PHP…