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.
git 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/vibe-test)<a href="https://agentmods.dev/rules/aishwaryshrivastav/vibe-testing/vibe-test"><img src="https://agentmods.dev/badge/rules/aishwaryshrivastav/vibe-testing/vibe-test/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/vibe-test"><img src="https://agentmods.dev/badge/rules/aishwaryshrivastav/vibe-testing/vibe-test.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.01279 | $0.01279 |
| Opus 5.5 | $0.00512 | $0.00512 |
| Sonnet 5.5 | $0.00256 | $0.00256 |
| Haiku 4.5 | $0.00128 | $0.00128 |
Grade A, and why
vibe-test 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe Testing — MCP Server for Browser Testing
You have access to the vibe-test MCP server which provides code-aware browser testing tools. Use these tools to test web applications by understanding their codebase, exploring pages, and executing test scenarios.
Quick Start Workflow
- Scan the codebase → understand routes, forms, coverage gaps
- Login (if app requires auth) → establish an authenticated browser session
- Explore pages → discover elements, click everything, observe what works/breaks
- Execute scenarios → run specific test flows (generated or custom)
- Generate report → HTML report with screenshots and coverage analysis
- Cleanup → close browsers when done
Available MCP Tools
scan_codebase
Call first. Analyzes the project source code to build a ProductModel:
- Detects framework (Next.js, React SPA, etc.)
- Parses all routes (pages + API endpoints)
- Extracts forms, buttons, dialogs, features per route
- Reads existing test files for coverage mapping
- Identifies gaps and generates test scenarios
{ "codebase_path": "/path/to/project", "url": "https://staging.myapp.com" }
login
Establish an authenticated browser session. Uses saved credentials from previous runs or accepts new ones.
{ "email": "[email protected]", "password": "pass123", "login_url": "/login" }
Returns: post-login screenshot, token state, API calls observed.
scan_page_elements
Navigate to a page and discover all interactive elements without interacting with them. Returns element types, selectors, text, and a page screenshot.
{ "route": "/dashboard", "authenticated": true }
explore_page
Full "senior tester" exploration — clicks every button, fills every input, tests every tab, observes API calls. Returns detailed interaction outcomes.
{ "route": "/dashboard", "authenticated": true }
execute_scenario
Run a specific test scenario (sequence of steps). You can use scenarios from scan_codebase output or construct custom ones.
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 · 147 lines · 1,279 tokens per session scan A 6a1a265e6bf4
vibe-test is a cursor rule published in the GitHub repository AishwaryShrivastav/vibe-testing (17 stars, last pushed 8d ago), licensed MIT. It adds 1,279 tokens to every session, about $0.0051 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
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…
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-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…
cursor-rules
Playwright E2E testing rules for {{PROJECTNAME}}; the full skill lives in .agents/skills/playwright-e2e.