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 performance-testinggit 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/performance-testing)<a href="https://agentmods.dev/skills/aryan-jhaveri/mcp-statcan/performance-testing"><img src="https://agentmods.dev/badge/skills/aryan-jhaveri/mcp-statcan/performance-testing/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/performance-testing"><img src="https://agentmods.dev/badge/skills/aryan-jhaveri/mcp-statcan/performance-testing.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.00051 | $0.00697 |
| Opus 5.5 | $0.00020 | $0.00279 |
| Sonnet 5.5 | $0.00010 | $0.00139 |
| Haiku 4.5 | $0.00005 | $0.00070 |
Grade A, and why
performance-testing 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Performance Testing
A collection supplies realistic request sequences; postman performance run
adds concurrency and a load profile. This makes performance claims repeatable,
but only for the workload, data, and network path actually exercised.
Collections run directly: converting with postman-to-k6 is not required.
- Choose the failure mode before the profile:
fixedtests sustained concurrency,ramp-upexplores degradation as load grows,spiketests sudden surges, andpeaktests staying near maximum load. Reuse the collection's auth and assertions, and check that its operations and data represent the workload rather than repeating one unusually cheap request. - Establish the target, VU count, duration, and effects of write requests before sending load. Existing user authorization for that scope is enough; resolve missing limits before stressing a shared or production service. Thresholds are evaluated after the run, so a failing gate will not stop traffic early. A small initial run can expose wiring failures before a larger authorized test.
- Choose the runner by reachability and capacity.
localuses this machine or CI runner; its CPU or network can become the bottleneck.postman-cloudmoves generation to Postman's infrastructure, whilepostman-cloud-static-ipsupports targets with IP allowlists. Verify reachability before interpreting connection failures as service capacity. - Set thresholds that represent the user's objective, such as
--pass-if "less_than(p95, 500)". Supported metrics includeavg,p90,p95,p99,error_rate, andrps; latency alone can look good when requests fail quickly. Usepostman performance run -hfor current syntax, units, and runner-specific options. - Isolate test data where concurrent writes would collide. datasets
supports controlled row distribution across VUs; setup/teardown collections
on hosted runners execute once around the test, not once per iteration.
--use-mockcan baseline collection/script overhead, but its numbers cannot establish the real backend's capacity.
What ships with it
5 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 · 56 lines · 51 tokens per session scan A 7f76f94adcd2
performance-testing is a skill published in the GitHub repository Aryan-Jhaveri/mcp-statcan (7 stars, last pushed yesterday), licensed MIT. It adds 51 tokens to every session and 697 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
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
testing
Testing and code quality context for Jest, React Testing Library, ESLint, and test patterns. Use when writing tests or fixing linting issues.
testing
Verify a Skyvern deployment is working correctly by smoke-testing the backend API, frontend rendering, browser session provisioning, and workflow execution. Use when the user says 'is Skyvern working', 'test my deployment', 'verify the installation', 'smoke test', or needs to check that a self-hosted or local Skyvern…
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.
capture-api-response-test-fixture
For provider response parsing tests, we aim at storing test fixtures with the true responses from the providers (unless they are too large in which case some cutting that does not change semantics is advised).
emulate-seed
Generate emulate seed configs for stateful API emulation. Wraps Vercel's emulate tool for GitHub, Vercel, Google OAuth, Slack, Apple Auth, Microsoft Entra, AWS, Okta, Clerk, Resend, Stripe, and MongoDB Atlas APIs — full state machines, not mocks. Use when setting up test environments, CI pipelines, integration tests…