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 application-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/application-testing)<a href="https://agentmods.dev/skills/aryan-jhaveri/mcp-statcan/application-testing"><img src="https://agentmods.dev/badge/skills/aryan-jhaveri/mcp-statcan/application-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/application-testing"><img src="https://agentmods.dev/badge/skills/aryan-jhaveri/mcp-statcan/application-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.00190 | $0.02471 |
| Opus 5.5 | $0.00076 | $0.00988 |
| Sonnet 5.5 | $0.00038 | $0.00494 |
| Haiku 4.5 | $0.00019 | $0.00247 |
Grade A, and why
application-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 — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Application Test
Overview
Requires a Playwright project in the repository. Without Playwright e2e tests there is nothing to capture — Playwright is the only supported runner.
postman application test does not send its own requests. It:
- Spawns your Playwright test command (e.g.
npx playwright test) - The capture plugin intercepts network traffic and writes it as artifacts
- The CLI reads those artifacts, matches each request against your collections, and runs any
pm.testassertions saved in the matched items - Publishes results to Application Inventory in your Postman workspace
The question it answers: did my app's actual HTTP calls conform to the collection contract? Not "does this endpoint respond correctly" — for that, use postman collection run.
Application Inventory is where results are published — a Postman dashboard that records each run's Playwright test results alongside captured/matched/assertion counts, giving you a combined view of test health and API contract conformance across runs.
Prerequisites
All postman app commands must be run from the repository root — that is where postman.config.cjs, .postman/resources.yaml, and postman/collections/ are expected to live.
Assess each prerequisite against the current state of the repository before taking any action. Most will already be satisfied in an established project; only act on what is actually missing.
Playwright project
This skill applies only when the repository has Playwright e2e tests. Verify that a playwright.config.* file exists and @playwright/test is listed as a project dependency. If neither is present, stop — there is nothing to capture and this skill does not cover Playwright setup.
Authentication
Publishing results to Postman requires credentials. Authenticate only when workspace publishing is needed:
- If
POSTMAN_API_KEYis in the environment, runpostman login --with-api-key "$POSTMAN_API_KEY". This is the expected path in CI and agentic contexts. - If the key is not available, surface the gap to the user — do not initiate
postman loginin an agentic context, as it requires a human to complete a browser flow.
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 · 145 lines · 190 tokens per session scan A 2531d4485bf5
application-testing is a skill published in the GitHub repository Aryan-Jhaveri/mcp-statcan (7 stars, last pushed yesterday), licensed MIT. It adds 190 tokens to every session and 2,471 once invoked, about $0.0008 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
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.
e2e-testing
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies. Use when writing Playwright tests, structuring page objects, or fixing flaky E2E runs in CI.
dogfood
Exploratory QA of web apps: find bugs, evidence, reports.
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.
langbot-testing
Test LangBot WebUI and core product flows with an automated browser and backend logs. Use when validating the configured LangBot frontend, pipeline Debug Chat, model provider setup and test buttons, bot and knowledge-base UI flows, or troubleshooting failed LangBot end-to-end tests.