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/roedyrustam/vibes-plugWrote 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/roedyrustam/vibes-plug/vibes-plug-testing)<a href="https://agentmods.dev/rules/roedyrustam/vibes-plug/vibes-plug-testing"><img src="https://agentmods.dev/badge/rules/roedyrustam/vibes-plug/vibes-plug-testing/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/roedyrustam/vibes-plug/vibes-plug-testing"><img src="https://agentmods.dev/badge/rules/roedyrustam/vibes-plug/vibes-plug-testing.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.00000 | $0.00274 |
| Opus 5.5 | $0.00000 | $0.00110 |
| Sonnet 5.5 | $0.00000 | $0.00055 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
vibes-plug-testing 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 today.
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
Vibes-Plug Testing & Verification Standards (2026 Edition)
When writing or executing tests, Cursor AI MUST enforce these standards:
1. Autonomous TDD & Quality Gate
- Test-First Execution: When implementing new features, write failing tests first (Red), implement the minimum code to pass (Green), then refactor (Clean).
- Zero Mocks in Production Logic: Mocks are strictly confined to test fixtures. Never commit fake mocks or in-memory array stubs into production service code.
- Determinism: Eliminate flaky tests by utilizing deterministic clocks (
vi.useFakeTimers()or Playwright Clock API) and avoiding non-deterministicsleep()intervals. - Coverage Criteria: Test both the happy path and edge cases: invalid inputs, boundary values, permission denials, and network failure modes.
- E2E Standards: Use ARIA role selectors (
getByRole,getByLabel) rather than brittle CSS or XPath selectors.
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.
- today First seen · 17 lines · 0 tokens per session scan A 7b8b70a155c9
vibes-plug-testing is a cursor rule published in the GitHub repository roedyrustam/vibes-plug (114 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 274 tokens. 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-10-27.
Other cursor rules, from other repositories
testing
USE WHEN: Writing tests with Vitest, Testing Library and MSW.
testing-master
Automated test strategies, unit testing, and E2E testing guidelines. / TR: Test stratejileri, birim testleri (unit test) ve e2e testler yazmak için yetenek.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.