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/.cursorrulesgit 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/rules/aishwaryshrivastav/vibe-testing/cursorrules)<a href="https://agentmods.dev/rules/aishwaryshrivastav/vibe-testing/cursorrules"><img src="https://agentmods.dev/badge/rules/aishwaryshrivastav/vibe-testing/cursorrules/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/rules/aishwaryshrivastav/vibe-testing/cursorrules"><img src="https://agentmods.dev/badge/rules/aishwaryshrivastav/vibe-testing/cursorrules.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.00458 | $0.00458 |
| Opus 5.5 | $0.00183 | $0.00183 |
| Sonnet 5.5 | $0.00092 | $0.00092 |
| Haiku 4.5 | $0.00046 | $0.00046 |
Grade A, and why
cursorrules 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
Vibe Test — Cursor Rules
This is the vibe-test source repository (the MCP server + CLI tool for browser testing).
Project Overview
vibe-test is published as an npm package (npx vibe-test) and provides 12 MCP tools for AI-powered browser testing via Playwright. Users run npx vibe-test init in their project and then their AI editor can test their app.
Architecture
src/cli.ts— CLI entry + MCP server launcher (--mcpflag)src/mcp-server.ts— 12 MCP tools via JSON-RPC stdiosrc/engine/context/— Static code analysis (framework detection, route parsing, scenario generation)src/engine/browser/— Playwright execution (runner, explorer, verifier)src/engine/memory/— Persistent learning across runssrc/engine/reporter/— HTML report generation
When editing this repo
- TypeScript strict mode, ESM modules (
"type": "module"in package.json) - Build:
npm run build(tsc → dist/) - The MCP server communicates over stdio — all output must go to stderr or be MCP JSON-RPC responses
- Tool handlers are in
mcp-server.ts— add new tools by: (1) adding toListToolsRequestSchemahandler, (2) adding toCallToolRequestSchemaswitch, (3) implementing the handler function get_contexttool is the most important — it returns source files with relevance scoring so the LLM knows real selectors
Key patterns
- Session state between MCP tool calls:
sessionobject inmcp-server.ts - Framework detection:
detector.ts— add new frameworks here - Port auto-detection:
detectBaseUrl()indetector.ts - Monorepo support:
detectMonorepo()+findFrontendApp()indetector.ts - Init templates: the string constants at the top of
cli.ts— these get written to user projects
Publishing
Package name: vibe-test. Build → npm publish.
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 · 37 lines · 458 tokens per session scan A eb15be30d9d9
cursorrules is a cursor rule published in the GitHub repository AishwaryShrivastav/vibe-testing (17 stars, last pushed 12d ago), licensed MIT. It adds 458 tokens to every session, about $0.0018 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 cursor rules, from other repositories
true-platform-testing
End-to-end Katalon True Platform testing workflow and lifecycle router. Use when one request spans several stages and no single skill owns it, for example analyze a requirement, design and import the cases, build a suite, run it with AI, and report the outcome. Also use to route any testing request across the 7-stage…
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
playwright-execute
Run Playwright tests or suites and upload the resulting report to Katalon True Platform. Use when you need to execute Playwright scripts, package scripts, spec files, projects, or suites, configure or verify @katalon/playwright-reporter, upload Playwright reports with Katalon CLI/reporter commands, and verify uploaded…
test-case-to-playwright
Convert Katalon True Platform/TestOps manual test cases, test suites, or requirement-linked cases into Playwright TypeScript automation. Use when you need to fetch/read Katalon Platform test cases and implement Playwright scripts, create or adapt a Playwright framework, apply Page Object Model and fixtures, or…
test-maintenance
Maintain and evolve a Katalon True Platform/TestOps regression suite as the application changes. Use when you need to detect which tests broke or became flaky from stability and result history, diagnose whether a case needs repair vs regeneration, repair test assets (update, move, reorganize cases), refresh coverage…
cypress-integration-testing-cursorrules-prompt-file
Cursor rules for Cypress development with integration testing.