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 agentmods add instructions/jasonboy/msw-mcp/agents-mdgit 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/instructions/jasonboy/msw-mcp/agents-md)<a href="https://agentmods.dev/instructions/jasonboy/msw-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/jasonboy/msw-mcp/agents-md.svg" alt="Measured on agentmods" 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 | $0.00931 | $0.00931 |
| Opus 5 | $0.00465 | $0.00465 |
| Sonnet 5 | $0.00186 | $0.00186 |
| Haiku 4.5 | $0.00093 | $0.00093 |
Grade A, and why
msw-mcp AGENTS.md 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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monorepo Overview
This project is a monorepo managed by pnpm and Turborepo. It is designed to house multiple packages related to MSW (Mock Service Worker) and MCP (Model Context Protocol).
Tooling
- Package Manager: pnpm (Workspaces)
- Build System: Turborepo
- Linting & Formatting: Prettier, lint-staged, Husky
- Language: TypeScript
Structure
packages/: Contains the individual workspace packages.msw-mcp: The core MCP server for MSW AI interaction.
package.json(root): Orchestrates the workspace, shared dependencies, and scripts.turbo.json: Defines the task pipeline and caching strategy.
Common Commands
pnpm install: Install all dependencies across the workspace.pnpm run build: Build all packages using Turbo.pnpm run test: Run all package tests via Turbo.pnpm run test:coverage: Run tests with v8 coverage reporting.pnpm run format: Format the entire codebase.pnpm turbo run <task>: Run specific Turbo tasks.
Testing
The repo uses Vitest (v4.x). Test dependencies live in the root package.json; each package has its own vitest.config.ts and "test" script.
When to add tests
Add or update tests whenever you change behavior — new features, bug fixes, refactors, or CLI/MCP tool output. Skip tests only for docs-only or purely cosmetic changes.
Conventions
- Location: Co-locate tests as
src/**/*.test.tsnext to the code they cover. - Build: Test files are excluded from
tscoutput via each package'stsconfig.jsonexclude. - Environment: Node for
core,msw-cli, andmsw-mcp;jsdomfor@msw-mcp/client(browser APIs). - Style: Prefer unit tests with injected/mocked dependencies. Use integration tests sparingly for real WebSocket/HTTP round-trips (see
packages/core/src/server.integration.test.ts). - Scope: Test real behavior and edge cases — not trivial getters or framework wiring. Mock
console.errorwhen exercising expected error paths to keep output clean.
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.
- 4d ago First seen · 70 lines · 931 tokens per session scan A 8131798234d4
msw-mcp AGENTS.md is an instructions file published in the GitHub repository JasonBoy/msw-mcp (81 stars, last pushed 2mo ago), licensed MIT. It adds 931 tokens to every session, about $0.0047 per session on Opus 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 instructions, from other repositories
intelligent-terminal rust.instructions.md
Concise Rust coding conventions for this repository.
InvestSkill GEMINI.md
Gemini CLI instructions for yennanliu/InvestSkill, covering investskill — gemini cli setup & usage guide, installation & setup, quick start, navigate to the investskill directory and start gemini cli (loads gemini.md automatically).
she-love-me CLAUDE.md
Instructions for 863401402/she-love-me, covering claude.md and 唯一工作流.
wayland-core copilot-instructions.md
Copilot instructions for FerroxLabs/wayland-core, covering ijfw rules, output discipline, memory routing, context discipline and cross-audit.
SeekMoney-ai CLAUDE.md
Claude Code instructions for zykooooooooo/SeekMoney-ai, covering claude.md, project overview, development commands, development and production.
slivingdoc AGENTS.md
AGENTS.md instructions for baalimago/slivingdoc, covering agents.md — slivingdoc, architecture, package map, event flow and startup wiring (main.go).