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/BetterTyped/hype-stackWrote 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/bettertyped/hype-stack/testing-philosophy)<a href="https://agentmods.dev/rules/bettertyped/hype-stack/testing-philosophy"><img src="https://agentmods.dev/badge/rules/bettertyped/hype-stack/testing-philosophy/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/bettertyped/hype-stack/testing-philosophy"><img src="https://agentmods.dev/badge/rules/bettertyped/hype-stack/testing-philosophy.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.00357 |
| Opus 5.5 | $0.00000 | $0.00143 |
| Sonnet 5.5 | $0.00000 | $0.00071 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
testing-philosophy 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
Testing Philosophy (all apps)
Test real code. No mocks unless physically impossible.
vi.mock is FORBIDDEN unless there is no other way. The only acceptable reason to mock is third-party integrations that are not available in the test environment (external SaaS APIs with no local equivalent). Everything internal — feature logic, hooks, helpers, utils, state — runs real. This also keeps tests fast by avoiding network calls to external services.
When a new third-party integration needs mocking, build a reusable mock helper in the app's testing directory (src/testing/mocks/ on the backend, src/testing/helpers/ on the frontend) so every test file imports a single function instead of duplicating setup. Keep mock helpers focused, typed, and documented so future tests get mocking for free.
Rules shared by every test file
- NEVER import vitest — globals are available.
- No
anytypes — type mocks properly, e.g.vi.fn<(args) => ReturnType>(). - Tests must be independent — each test creates its own data and cleans up after itself.
- Every test MUST use
// Arrange,// Act,// Assertcomments to clearly separate setup, execution, and verification. Skip// Arrangeonly when there is no setup. - No
try/catchfor error assertions — useexpect().rejects.
App-specific conventions live in the backend and frontend testing rules.
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 · 24 lines · 0 tokens per session scan A d61d072ef7e2
testing-philosophy is a cursor rule published in the GitHub repository BetterTyped/hype-stack (12 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 357 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-08-31.
Other cursor rules, from other repositories
upgrade-tests
// ✅ CORRECT: Upgrade package pattern await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
react-query-tests
// ✅ CORRECT: Legacy React Query pattern const ctx = konn() .beforeEach(() => createAppRouter()) .afterEach((ctx) => ctx?.close?.()) .done().
tanstack-react-query-tests
// ✅ CORRECT: Use await using for automatic cleanup await using ctx = testReactResource(appRouter, { server: { // server configuration }, client(opts) { return { links: [ httpLink({ url: opts.httpUrl, // client configuration }), ], }; }, }).
verify
Review implementation ownership and verify Plate packages, editor states and registry artifacts through their actual proof owners. Use before writing a plan's phase exits or proof gates, before checking, skipping, deferring or moving any plan proof gate to limits, before writing or changing any test, including…
benchmark
Measure and repair Plate/Slate performance, or review a performance design before running its applicable benchmark lanes. Use before writing, reviewing, running, rerunning, checking, skipping or deferring a performance gate, including a plan's scale gate, before writing a benchmark script, before explaining a…
common-fixes
Utility for VAN QA common validation fixes.