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/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/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/openstory-so/openstory/bun-test"><img src="https://agentmods.dev/badge/rules/openstory-so/openstory/bun-test.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.01138 | $0.01138 |
| Opus 5.5 | $0.00455 | $0.00455 |
| Sonnet 5.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 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.
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.
- 1mo 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 (685 stars, last pushed today), licensed MIT. It adds 1,138 tokens to every session, about $0.0046 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-08-30.
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.
python-general-coding-standards
A set of general standards for Python projects, including type hints, input checking, code style, security, web requests, background work, and tests. It also covers FastAPI-specific tasks such as CORS and authentication.