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/iHildy/jules-task-queueWrote 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/ihildy/jules-task-queue/vitest)<a href="https://agentmods.dev/rules/ihildy/jules-task-queue/vitest"><img src="https://agentmods.dev/badge/rules/ihildy/jules-task-queue/vitest/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/ihildy/jules-task-queue/vitest"><img src="https://agentmods.dev/badge/rules/ihildy/jules-task-queue/vitest.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.03726 |
| Opus 5.5 | $0.00000 | $0.01490 |
| Sonnet 5.5 | $0.00000 | $0.00745 |
| Haiku 4.5 | $0.00000 | $0.00373 |
Grade A, and why
vitest 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 13d 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 — 379 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: This rule file provides comprehensive best practices for using Vitest, covering code organization, testing strategies, performance, and security within Vitest projects. These guidelines ensure clean, maintainable, and reliable test suites. globs: .js,.jsx,.ts,.tsx,.vue,.svelte,.spec,.test.*
Vitest Best Practices and Coding Standards
This document outlines best practices for using Vitest to create reliable, maintainable, and performant test suites. It covers various aspects of testing, from code organization to performance considerations and security measures.
Project Tech Stack:
ALWAYS USE THE FOLLOWING IN CONJUNCTION WITH EACHOTHER TO HAVE A SAFE CODEBASE WHERE WE CAN MOVE FAST AND BREAK NOTHING
- Next.js
- Typescript + ESlint
- Zod + Prisma + tRPC + React Query
- Prisma (supabase) + Redis
- ShadCN + TailwindCSS v4
- Vitest Unit Tests
1. Code Organization and Structure
1.1 Directory Structure
-
Keep tests close to the source code: Place test files in the same directory as the components or modules they test. This improves discoverability and maintainability.
src/ components/ MyComponent.vue MyComponent.spec.ts MyComponent.test.ts # Alternative naming utils/ math.ts math.test.ts App.vue App.spec.ts
-
Use a dedicated
testsdirectory for end-to-end tests or shared utilities: For larger projects, atestsdirectory at the root level can house end-to-end tests, integration tests that require a specific environment, or shared testing utilities.tests/ e2e/ specs/ home.spec.ts support/ commands.ts unit/ utils.test.ts # Tests for general utilities integration/ db.setup.ts # Setup for integration tests src/ ...
1.2 File Naming Conventions
- Use consistent naming: Adopt a consistent naming scheme for test files. Common conventions include:
[component/module].spec.ts[component/module].test.ts[component/module].e2e.ts(for end-to-end tests)
- Consistent Case: Maintain a consistent casing convention (e.g., camelCase for variables, PascalCase for components). Use
kebab-casefor file names e.g.user-profile.tsxoruser.router.ts
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.
- 13d ago First seen · 379 lines · 3,726 tokens per session scan A cab33aa4ab3b
vitest is a cursor rule published in the GitHub repository iHildy/jules-task-queue (17 stars, last pushed 8mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,726 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-02.
Other cursor rules, from other repositories
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
gonavi-go
A Go coding rule set for the GoNavi repository, based on common Go style guides and the project's own conventions. It covers file structure, errors, context, concurrency, logging, and tests.
workflow-level3
Defines the standard workflow for Level 3 (Intermediate Feature) tasks, guiding through comprehensive planning, targeted creative design, structured implementation, detailed reflection, and feature-specific archiving.
reflection-basic
Basic reflection format for Level 2 Simple Enhancement tasks.
rule-calling-guide
Comprehensive guide for calling VAN QA rules.
common-fixes
Utility for VAN QA common validation fixes.