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 bootstrapgit 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/bootstrap)<a href="https://agentmods.dev/skills/aryan-jhaveri/mcp-statcan/bootstrap"><img src="https://agentmods.dev/badge/skills/aryan-jhaveri/mcp-statcan/bootstrap/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/bootstrap"><img src="https://agentmods.dev/badge/skills/aryan-jhaveri/mcp-statcan/bootstrap.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.00086 | $0.01728 |
| Opus 5.5 | $0.00034 | $0.00691 |
| Sonnet 5.5 | $0.00017 | $0.00346 |
| Haiku 4.5 | $0.00009 | $0.00173 |
Grade A, and why
bootstrap 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bootstrap Postman for This Repo
A local Postman project puts contracts, runnable requests, environments, and mocks beside implementation code so they can be inspected, diffed, and reviewed in a PR. A workspace binding connects that work to maintained shared context. Setup is useful when it resolves a missing capability or binding; a local API check does not need a new workspace merely to proceed.
Start with postman init
postman init is idempotent and safe to run in any project, including one
already initialized. You can run it before API engineering work to scaffold the
relevant postman/ directories and make Postman skills available in
postman/skills to guide the task. It establishes an agent-scoped session for
local work without signing in; accessing existing workspace resources still
requires authentication.
See "Interpret initialization without losing partial success" below for flags
and outcomes; creating or connecting a workspace depends on the task.
Resolve only the missing setup
Inspect postman --version, .postman/resources.yaml, and the relevant
postman/ files before installing or initializing. Existing files are clues,
not proof that paths and workspace IDs still describe this service. Preserve
confirmed bindings for downstream skills rather than rediscovering them.
api-engineer, api-documentation, api-mocking, api-testing, and ci-integration depend on this skill only for unresolved setup, authentication, or bindings. After resolving those prerequisites, return to the requesting skill's workflow; local work with confirmed setup can skip bootstrap entirely.
If the CLI is missing, use npm install -g postman-cli or the applicable
platform installer. Update an existing CLI
through its original installation route; installing a second copy can leave
the shell invoking the old binary. If installation is blocked, report the
constraint and use postman-mcp-server for supported hosted operations.
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 · 141 lines · 86 tokens per session scan A 5b2dc72aa033
bootstrap is a skill published in the GitHub repository Aryan-Jhaveri/mcp-statcan (7 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 1,728 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
meta-pre-commit-quality-gate
Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.
experiment-loop
Autonomous benchmark-driven experiment loop: propose a change, measure the metric, keep what improves it, revert what doesn't, repeat. Git is the ledger — every kept improvement is a commit. Every discarded attempt is a clean revert.
sup-coding
Coding workflow recipe (brainstorm → design → spec → plan → implement → review → verify → finish).
verification-before-completion
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always.
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.
setup-pre-commit
Set up Husky pre-commit hooks with lint-staged (Prettier), type checking, and tests in the current repo. Use when user wants to add pre-commit hooks, set up Husky, configure lint-staged, or add commit-time formatting/typechecking/testing.