bun-test

A set of coding instructions for running tests with Bun, a JavaScript runtime and test tool, including tests whose suite name contains “addition”.

In plain words
What is it for?
Use it as guidance for running test suites, setting up CI/CD checks, and producing test reports for systems such as GitLab.
Why use it?
It documents how to run these tests and connect them to automated build checks such as GitHub Actions and JUnit XML reports.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/takuya0206/slack_search_function_mcp/bun-test
Clone the repo
git clone --depth 1 https://github.com/takuya0206/slack_search_function_mcp

Made for: Cursor.

Per session 1,823 This file is loaded in full into every session.
When invoked 1,823 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin unknown No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.01823 $0.01823
Opus 5 $0.00911 $0.00911
Sonnet 5 $0.00365 $0.00365
Haiku 4.5 $0.00182 $0.00182

Measured 3d ago against content hash 4d3c634cc20c, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 3d 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.

.cursor/rules/bun-test.mdc · 256 lines

The source is not reproduced here

No licence file

A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.

Read it on GitHub

Changes

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.

  1. 3d ago First seen · 256 lines · 1,823 tokens per session scan A 4d3c634cc20c

Subscribe to this mod's changes

bun-test is a cursor rule published in the GitHub repository takuya0206/slack_search_function_mcp (4 stars, last pushed 1y ago), with no licence file. It adds 1,823 tokens to every session, about $0.0091 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-31.