Borrowing it
Nothing to install: this file belongs to bun913/playwright-min-network-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/bun913/playwright-min-network-mcp/main/CLAUDE.mdgit clone --depth 1 https://github.com/bun913/playwright-min-network-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/bun913/playwright-min-network-mcp/claude-md)<a href="https://agentmods.dev/instructions/bun913/playwright-min-network-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/bun913/playwright-min-network-mcp/claude-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.1 | $0.00703 | $0.00703 |
| Opus 5 | $0.00351 | $0.00351 |
| Sonnet 5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00070 | $0.00070 |
Grade A, and why
playwright-min-network-mcp CLAUDE.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 7d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Network Monitor MCP
Project Overview
Network monitoring MCP tool for Playwright browser automation. Provides 3 core tools: start_monitor, stop_monitor, get_recent_requests.
Technical Requirements
See @docs/technical-requirements.md for complete specifications.
Development Rules
- TDD: Follow t-wada's TDD methodology (Red → Green → Refactor)
- Single File: Edit one file at a time
- Quality Gates: After each file modification, ALWAYS run:
npm run lint- Check code qualitynpm run format- Format codenpm run test:ci- Run tests with coverage
- Build: Always run
npm run buildbefore testing - Tests: Validate all 3 tools work correctly
- Coverage: Maintain branch coverage ≥80%
- Browser: Auto-launch Chrome with CDP on port 9222
- Memory: Max 200 network requests in buffer
Implementation Priority
- Core MCP server structure (
src/index.ts) - Browser management (
src/browser.ts) - Network monitoring (
src/monitor.ts) - Type definitions (
src/types.ts)
Testing Strategy
Test Design Principles
- Testability: Every function must accept required state through parameters
- TDD Approach: Build small functions incrementally with Red → Green → Refactor
- BDD Structure: Use
describe()for SUT (System Under Test),it()for behavior + condition
Unit Test Rules
- Speed: Use mocks/fakes for fast execution, suitable for watch mode
- Contract Testing: Verify promises/contracts, avoid self-fulfilling prophecies
- ❌
expect(body).toBe("hoge123")when body is mocked as "hoge123" - ✅
expect(request.url).include("?name=hoge123")to verify proper parameter passing
- ❌
- Test Structure:
describe("NetworkMonitor")- target componentit("should throw errors when required options are not given")- behavior + condition
System Test Requirements
- MCP Integration: Test actual Playwright integration for happy path scenarios
- Real Browser: Launch Playwright to verify network request observation
- Console Validation: Assert against console.log output for network capture verification
- Minimal Coverage: Focus on essential happy path + required option validation
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.
- 7d ago First seen · 67 lines · 703 tokens per session scan A 5a490e80d4b8
playwright-min-network-mcp CLAUDE.md is an instructions file published in the GitHub repository bun913/playwright-min-network-mcp (9 stars, last pushed 1y ago), licensed MIT. It adds 703 tokens to every session, about $0.0035 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-31.
Other instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.