bun-runtime Cursor ruleA
bun-runtime from brendadeeznuts1111/betting-brain-v3 is a Cursor rule: instructions the Cursor agent follows in that repo.
mdr add brendadeeznuts1111/betting-brain-v3/.cursor/rules/bun-runtime.mdc@v5.0.0Pins v5.0.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 14 of 14 checks passed
- Kind
- Cursor rule
- Repository
- brendadeeznuts1111/betting-brain-v3
- Path
.cursor/rules/bun-runtime.mdc- Versions recorded
- 5
- Latest version
- v5.0.0, committed Oct 8, 2025
- First version recorded
- Oct 7, 2025
- Size
- 6,055 bytes
- Repository stars
- 8
- License
- MIT
Bun runtime patterns and best practices.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Bun Runtime Rules
## 🔍 Code Searchability Patterns
### Find Bun Runtime Issues with ast-grep
```bash
# Find incorrect process spawning (should use processManager)
ast-grep --pattern 'Bun.spawn($$$)' src/
ast-grep --pattern 'import { spawn } from "bun"' src/
ast-grep --pattern 'import { spawn } from "child_process"' src/
sg -p 'Bun.spawn' src/
sg -p 'from "child_process"' src/
# Find Node.js fs usage (should use Bun file APIs)
ast-grep --pattern 'import fs from "fs"' src/
ast-grep --pattern 'import { readFile } from "fs/promises"' src/
sg -p 'from "fs"' src/
sg -p 'from "fs/promises"' src/
# Find incorrect test imports (should use bun:test)
ast-grep --pattern 'import { describe, test, expect } from "vitest"' tests/
ast-grep --pattern 'import { describe, test, expect } from "@jest/globals"' tests/
sg -p 'from "vitest"' tests/
sg -p 'from "@jest/globals"' tests/
# Find npm/yarn usage (should use bun)
ast-grep --pattern 'npm install' scripts/
ast-grep --pattern 'yarn install' scripts/
sg -p 'npm install' scripts/
sg -p 'yarn install' scripts/
```
### Bun Runtime Discovery Commands
```bash
# Find all Bun-specific patterns
sg search 'Bun.' src/
sg search 'bun:' src/
…Read the whole file at its exact version.
How to install
mdr add brendadeeznuts1111/betting-brain-v3/.cursor/rules/bun-runtime.mdc@sha256:31633f571231339cThe line at the top of this page pins the label v5.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_2yxnwuyg6drarrd6)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in brendadeeznuts1111/betting-brain-v3/.cursor/rules/bun-runtime.mdc since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of bun-runtime.mdc from somewhere else? Ask it: where did my bun-runtime.mdc come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Oct 7, 2025 and Oct 8, 2025, more than one a day.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v5.0.0 latest | 2025-10-08 | 154694c | 6,055 B | A | view · diff |
| v5.0.0 | 2025-10-08 | 3f79e5a | 4,590 B | A | view · diff |
| v4 | 2025-10-08 | 4a59e8e | 3,648 B | A | view · diff |
| git:20251007.8d64d27 | 2025-10-07 | 8d64d27 | 3,306 B | A | view · diff |
| git:20251007.d4e620d | 2025-10-07 | d4e620d | 1,924 B | A | view |
Installed this file, say at bun-runtime.mdc? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
Audit of the latest version
- pass: Size between 200 bytes and 200 KB (6055 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
brendadeeznuts1111/betting-brain-v3 · 8 stars · license MIT · pushed 2026-11-10 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2yxnwuyg6drarrd6 GET https://markdownregistry.com/api/v1/resolve?ref=brendadeeznuts1111/betting-brain-v3/.cursor/rules/bun-runtime.mdc GET https://markdownregistry.com/api/v1/blob/31633f571231339c389a33ff0753584592ca423da084fcab5c44661173329b31
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: Cursor rules vs AGENTS.md · which agent file does what.
More from brendadeeznuts1111/betting-brain-v3
Every file in brendadeeznuts1111/betting-brain-v3