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/timurgaleev/vibestackWrote 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/timurgaleev/vibestack/tests)<a href="https://agentmods.dev/rules/timurgaleev/vibestack/tests"><img src="https://agentmods.dev/badge/rules/timurgaleev/vibestack/tests/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/timurgaleev/vibestack/tests"><img src="https://agentmods.dev/badge/rules/timurgaleev/vibestack/tests.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.00374 | $0.00374 |
| Opus 5.5 | $0.00150 | $0.00150 |
| Sonnet 5.5 | $0.00075 | $0.00075 |
| Haiku 4.5 | $0.00037 | $0.00037 |
Grade A, and why
tests 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 23d 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
Testing Requirements
Test Value Bar
A test earns its place by protecting behavior a real regression would break. Write one only when all four questions have an answer:
- What observable behavior, invariant or contract does it protect?
- What credible regression makes it fail?
- Why does existing coverage not already catch that?
- Does it need a production seam no production caller needs? If so, test at the real boundary instead.
Weak tests are not coverage: a smoke test, an existence check, or "it doesn't throw" never counts as covering a path. A regression test is proven red against the code before the fix, then green after it. Red means the test executed and failed for the intended reason — an import error, a missing fixture or a typo in the assertion is not red.
Testing Workflow
Recommended workflow:
- Write tests for new functionality
- Run tests to verify they fail (if testing new code)
- Implement functionality
- Run tests to verify they pass
- Refactor as needed while keeping tests green
Troubleshooting Test Failures
- Read error messages carefully
- Check test isolation - tests should not share state
- Verify mocks are correct
- Fix implementation, not tests (unless tests are wrong)
- Use debugger to trace execution flow
Test Writing Guidelines
- Fast: Unit tests should run in <10ms
- Isolated: No shared state between tests
- Deterministic: Same input always produces same output
- Readable: Tests serve as documentation
- Focused: Test one thing per test case
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.
- 23d ago Changed · +2 lines · +31 tokens per session 7ed459e2051c
- 25d ago Changed · +8 lines · +81 tokens per session 5a0278239075
- 1mo ago First seen · 40 lines · 262 tokens per session scan A a80a60f0aeb0
tests is a cursor rule published in the GitHub repository timurgaleev/vibestack (7 stars, last pushed 20d ago), licensed MIT. It adds 374 tokens to every session, about $0.0015 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-09-19.
Other cursor rules, from other repositories
testing
Cursor rule "testing" from kanyun-inc/reskill, covering testing rules, testing philosophy, spec-driven tdd workflow, benefits of test-first approach and example: adding --dry-run option.
unit-tests-tdd
TDD for behavior changes; co-located tests; keep touched areas well covered.
every-error-regression-test
Mandatory regression test for every discovered defect or failure (non-negotiable).
tdd-patterns
Rigorous Test-Driven Development (TDD) with DUnitX, naming and dependency injection for isolation with fakes and mocks.
android_unit_testing_bdd
Unit testing best practices with BDD style.
unity-testing
Unity Test Framework (Production Standards).