Borrowing it
Nothing to install: this file belongs to AishwaryShrivastav/vibe-testing. 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/AishwaryShrivastav/vibe-testing/main/CLAUDE.mdgit clone --depth 1 https://github.com/AishwaryShrivastav/vibe-testingWrote 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/aishwaryshrivastav/vibe-testing/claude-md)<a href="https://agentmods.dev/instructions/aishwaryshrivastav/vibe-testing/claude-md"><img src="https://agentmods.dev/badge/instructions/aishwaryshrivastav/vibe-testing/claude-md/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/instructions/aishwaryshrivastav/vibe-testing/claude-md"><img src="https://agentmods.dev/badge/instructions/aishwaryshrivastav/vibe-testing/claude-md.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.01145 | $0.01145 |
| Opus 5.5 | $0.00458 | $0.00458 |
| Sonnet 5.5 | $0.00229 | $0.00229 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
vibe-testing 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 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.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe Test — Code-Aware Browser Testing Agent
This is the vibe-test source repository. It's an MCP server + CLI for AI-powered browser testing.
What This Project Does
vibe-test gives AI coding assistants (Claude Code, Cursor, Windsurf, etc.) 14 browser testing tools via MCP. When a user asks "test the login flow", the AI uses these tools to:
- Read the source code (understand real field names, routes, selectors)
- Open a real Playwright browser
- Execute test steps, take screenshots
- Report what works and what breaks — including regressions vs the previous run
Architecture
src/
├── cli.ts # CLI entry: vibe-test run/converge/init/reset/report + --mcp flag
├── mcp-server.ts # MCP server (14 tools via JSON-RPC stdio)
└── engine/
├── index.ts # VibeTester orchestrator (run + converge, emits snapshot_diff)
├── converge.ts # Iterative coverage loop (baseline + follow-up rounds)
├── context/ # Static code analysis (no browser)
│ ├── index.ts # Builds ProductModel; writes route manifest + diffs scans
│ ├── detector.ts # Framework detection + monorepo detection + port auto-detect
│ ├── router.ts # Route parsing per framework
│ ├── extractor.ts # Extract forms, buttons, dialogs, features
│ ├── test-reader.ts # Parse existing Jest/Cypress/Playwright tests
│ ├── gap-analyzer.ts # Score untested routes by priority
│ └── enricher.ts # Generate TestScenarios from gaps
├── browser/ # Playwright execution
│ ├── runner.ts # Execute scenarios step-by-step
│ ├── explorer.ts # Click everything, monitor APIs
│ └── verifier.ts # Heuristic pass/fail (no LLM)
├── memory/ # Persist learning across runs
│ ├── index.ts # MemoryManager — selectors, timings, credentials, flaky routes
│ └── manifest.ts # Route manifest + run snapshot diffing (regression detection)
├── reporter/ # Generate HTML reports
└── coverage-gaps.ts # Post-execution gap analysis
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 Changed bddea497a3ff
- 1mo ago Changed 42f1f3c18163
- 1mo ago First seen · 93 lines · 1,145 tokens per session scan A 129059eb37a6
vibe-testing CLAUDE.md is an instructions file published in the GitHub repository AishwaryShrivastav/vibe-testing (17 stars, last pushed 12d ago), licensed MIT. It adds 1,145 tokens to every session, about $0.0046 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-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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.