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 JasonBoy/msw-mcp --skill msw-setupgit clone --depth 1 https://github.com/JasonBoy/msw-mcpWrote 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/jasonboy/msw-mcp/msw-setup)<a href="https://agentmods.dev/skills/jasonboy/msw-mcp/msw-setup"><img src="https://agentmods.dev/badge/skills/jasonboy/msw-mcp/msw-setup/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/jasonboy/msw-mcp/msw-setup"><img src="https://agentmods.dev/badge/skills/jasonboy/msw-mcp/msw-setup.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.00052 | $0.00517 |
| Opus 5.5 | $0.00021 | $0.00207 |
| Sonnet 5.5 | $0.00010 | $0.00103 |
| Haiku 4.5 | $0.00005 | $0.00052 |
Grade A, and why
msw-setup 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 1mo ago.
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.
What it actually says
msw-setup
Project scaffolding for MSW + the MCP client bridge. For runtime handler changes after setup, use the msw-cli skill.
Workflow
- Run
msw-cli setupin the project root (optional:--framework vite). - Follow the printed setup guide step by step (detect bundler, install deps, create
mocks/, env vars, entry point). - Run
msw-cli openand set the app's WebSocket URL to the URL from the output. - Run
msw-cli statusafter starting the dev server — confirmconnected: true(this only proves the WebSocket bridge, not that the first browser requests were intercepted). - Hard reload the app and confirm in DevTools → Network that initial API calls are mocked. This catches render-before-mock races that
msw-cli statusmisses. - Use
msw-cli add(and related commands) to manage mocks at runtime.
Do not duplicate the full setup guide in chat — execute from msw-cli setup output.
Notes
- Ask permission before
npm install/npx msw init(as the guide describes). - The WebSocket URL env var name depends on the framework:
NEXT_PUBLIC_MSW_WS_URL(Next.js),VITE_MSW_WS_URL(Vite), orMSW_WS_URL(Rspack/Rsbuild/Webpack) — must match the port frommsw-cli open. (MCP_SERVER_URLis accepted as a legacy fallback.) - Next.js App Router:
app/layout.tsxis a Server Component; the MSW bootstrap must be a'use client'gate so the app subtree does not mount (and fetch) beforeinitMocks()finishes. Follow the guide’s gatedMswProviderpattern — do not start MSW in a paralleluseEffectwhile rendering the full tree. - MCP users can still use
/msw-setupin an MCP client; the same guide backs both paths.
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.
- 1mo ago First seen · 29 lines · 52 tokens per session scan A 07cfcaa16815
msw-setup is a skill published in the GitHub repository JasonBoy/msw-mcp (81 stars, last pushed 4mo ago), licensed MIT. It adds 52 tokens to every session and 517 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-08-30.
Other skills, from other repositories
review-prs
Review a GitHub pull request in the googleapis/mcp-toolbox repo against the team's reviewer checklist: PR title/description conventions, linked issue, logic errors and unhandled edge cases, breaking changes, test coverage, docs updates, security (input handling), and new dependencies. Use whenever a maintainer asks…
bad-case-to-dpo
A guide to turning failed production agent runs into training and evaluation data. It explains how to find the first mistake, create preference examples for DPO (Direct Preference Optimization), and check that a fix does not damage other tasks.
eval-dataset-design
A guide to creating reliable test sets for AI agents. Each evaluation task includes the request, the simulated user's behaviour, a reset starting state, and a success check that can be independently verified.
omh-agent-evaluation
This is a Hermes-native agent-evaluation workflow skill.
llm-as-judge-evaluation
Evaluate LLM outputs using frontier models as judges. Use for pairwise model comparison, quality scoring with custom rubrics, and automated evaluation pipelines. Covers position bias mitigation, statistical significance, and generating preference data for DPO/RLHF.
golang-testing
Production-ready Golang tests — table-driven tests, testify suites and mocks, parallel tests, fuzzing, fixtures, goroutine leak detection with goleak, snapshot testing, code coverage, integration tests, idiomatic test naming. Use when writing or reviewing Go tests, choosing a testing approach, setting up Go test CI…