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/phishark-git/phishark-playwright-mcp/agents-mdgit clone --depth 1 https://github.com/phishark-git/phishark-playwright-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/phishark-git/phishark-playwright-mcp/agents-md)<a href="https://agentmods.dev/instructions/phishark-git/phishark-playwright-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/phishark-git/phishark-playwright-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.00276 | $0.00276 |
| Opus 5 | $0.00138 | $0.00138 |
| Sonnet 5 | $0.00055 | $0.00055 |
| Haiku 4.5 | $0.00028 | $0.00028 |
Grade A, and why
phishark-playwright-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.
What it actually says
Module instructions
- Purpose: provide the upstream Playwright MCP toolset with PhiShark preflight and browser-deep phishing protection.
- Upstream: derived from
microsoft/playwright-mcp; keepupstreamas the Microsoft remote and pin Playwright dependencies exactly. - Important files:
cli.js,index.js,src/phishark/,tests/phishark/,tests/phishark-security.spec.ts,.github/workflows/. - Contract: local stdio MCP; consumes
POST /api/v1/scan/preflightandPOST /api/v1/scan/browser-deepwithX-API-Key. - Commands: setup
npm ci; unit testnpm run test:phishark; browser testnpm test; buildnpm run build; package checknpm pack --dry-run. - Distribution: public npm package
@phishark/playwright-mcp; release publication is GitHub Actions and npm trusted-publisher only. There is no VDS or Cloud Run deployment.
Never log PHISHARK_API_KEY, raw HTML, screenshots, or sensitive request headers. Do not weaken fail-closed core compatibility checks, high/critical blocking, private-network defaults, or blocked-page response redaction. Upstream dependency changes require the compatibility and full browser test suites.
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 · 11 lines · 276 tokens per session scan A 00bb36d64827
phishark-playwright-mcp AGENTS.md is an instructions file published in the GitHub repository phishark-git/phishark-playwright-mcp (3 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 276 tokens to every session, about $0.0014 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
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).
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.
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 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).
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.