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.
npx agentmods add rules/openstory-so/openstory/bun-testgit clone --depth 1 https://github.com/openstory-so/openstoryWrote 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/openstory-so/openstory/bun-test)<a href="https://agentmods.dev/rules/openstory-so/openstory/bun-test"><img src="https://agentmods.dev/badge/rules/openstory-so/openstory/bun-test.svg" alt="Measured on agentmods" 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.01138 | $0.01138 |
| Opus 5 | $0.00569 | $0.00569 |
| Sonnet 5 | $0.00228 | $0.00228 |
| Haiku 4.5 | $0.00114 | $0.00114 |
Grade A, and why
bun-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 6d 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor/Claude Rules for Bun Test Mocking
Rule 1: Use mock.module() for Module-Level Mocking
When mocking entire modules, use mock.module(path, callback) (1) :
import { test, expect, mock } from "bun:test";
mock.module("./module", () => {
return {
foo: "bar",
};
}) ;
test("mock.module", async () => {
const esm = await import("./module") ;
expect(esm.foo) .toBe("bar") ;
const cjs = require("./module") ;
expect(cjs.foo) .toBe("bar") ;
}) ;
Rule 2: Use spyOn() for Individual Function Mocking
To mock specific functions from imported modules, use spyOn() with mockImplementation() , (2) :
import { test, expect, spyOn } from "bun:test";
const ringo = {
name: "Ringo",
sayHi() {
console.log(`Hello I'm ${this.name}`) ;
},
};
const spy = spyOn(ringo, "sayHi") ;
test("spyon", () => {
expect(spy) .toHaveBeenCalledTimes(0) ;
ringo.sayHi() ;
expect(spy) .toHaveBeenCalledTimes(1) ;
}) ;
Rule 3: Mock Return Values Using Mock Methods
For mocking return values, use the mock function methods (1) :
import { mock } from "bun:test";
const random = mock((multiplier: number) => multiplier * Math.random() ) ;
random(2) ;
random(10) ;
random.mock.calls;
// [[ 2 ], [ 10 ]]
random.mock.results;
// [
// { type: "return", value: 0.6533907460954099 },
// { type: "return", value: 0.6452713933037312 }
// ]
Rule 4: Use Jest-Compatible Syntax
Bun supports Jest-compatible mocking syntax :
import { test, expect, jest } from "bun:test";
const random = jest.fn(() => Math.random() ) ;
test("random", async () => {
const val = random() ;
expect(val) .toBeGreaterThan(0) ;
expect(random) .toHaveBeenCalled() ;
expect(random) .toHaveBeenCalledTimes(1) ;
}) ;
Rule 5: Mock Fetch Using spyOn (Community Solution)
For mocking fetch, use spyOn on the global object (3) :
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.
- 6d ago First seen · 170 lines · 1,138 tokens per session scan A f0d02088982a
bun-test is a cursor rule published in the GitHub repository openstory-so/openstory (574 stars, last pushed yesterday), licensed MIT. It adds 1,138 tokens to every session, about $0.0057 per session on Opus 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-30.
Other cursor rules, from other repositories
use-contract-ir-factories
Use factory functions for creating ContractIR objects instead of manual object creation.
mockito
This guide provides definitive best practices for writing robust, maintainable, and readable unit tests using Mockito with JUnit 5, focusing on modern patterns and common pitfalls.
python-general-coding-standards
应用一般 Python 编码标准,包括类型提示、使用 Pydantic 进行输入验证、后台任务、CORS 处理、安全工具、PEP 8 合规性和全面测试。.
spec-for-ut
Unit testing is essential to ensure the reliability and stability of code, especially for React components and functions. Adhering to best practices and ensuring high test coverage is critical to maintaining a robust codebase.
unit-testing-standards
Cursor rule "unit-testing-standards" from adobecom/da-express-milo, covering unit testing standards, testing philosophy, testing framework stack, test structure patterns and 1. standard test file organization.
qa
This document defines the role and responsibilities of a Senior QA Engineer for the Sunra Clients project, a multi-language SDK suite that provides client libraries for Java/Kotlin, JavaScript/TypeScript, and Python, along with comprehensive examples and server proxy utilities.