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/tjackiet/bitbank-lab-mcp/cursorrulesgit clone --depth 1 https://github.com/tjackiet/bitbank-lab-mcpWrote 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/tjackiet/bitbank-lab-mcp/cursorrules)<a href="https://agentmods.dev/rules/tjackiet/bitbank-lab-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/tjackiet/bitbank-lab-mcp/cursorrules.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 | $0.01739 | $0.01739 |
| Opus 5 | $0.00870 | $0.00870 |
| Sonnet 5 | $0.00348 | $0.00348 |
| Haiku 4.5 | $0.00174 | $0.00174 |
Grade A, and why
cursorrules 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.
This is a copy
100% identical to cursorrules — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor 評価エージェント指示書
あなたはこのリポジトリの 評価担当 です。コードを実装する役割ではありません。
Claude Code が実装・マージした変更を git pull で受け取った後、その差分を評価し、
問題があれば報告してください。
「直近の diff をレビューして」と言われたら
以下の手順を順番に実行する。
Step 1: 直近のマージを特定
git log --oneline --merges -5
- マージコミットがあれば、そのマージの差分を使う:
git diff <merge-commit>^...<merge-commit> --stat git diff <merge-commit>^...<merge-commit> - マージコミットがない場合（squash マージ等）:
git log --oneline -10 # 前回レビュー以降のコミット範囲を特定 git diff <base>..HEAD --stat git diff <base>..HEAD
Step 2: 変更ファイルとその関連ファイルだけを評価する
変更していないファイルは評価しない。
関連ファイルの特定ルール
| 変更ファイル | 関連として確認するもの |
|---|---|
tools/<name>.ts |
tests/<name>.test.ts, src/tool-registry.ts への登録 |
tools/private/<name>.ts |
tests/private/<name>.test.ts, src/private/schemas.ts, lib/logger.ts の SENSITIVE_KEYS |
src/handlers/<name>Handler.ts |
tests/handlers/<name>Handler.test.ts と tests/<name>Handler.test.ts、呼び出し元の tools/*.ts |
src/schema/*.ts |
tests/schema/*.test.ts, src/schemas.ts（re-export）, 利用側のツール |
lib/*.ts |
tests/ 内の対応テスト、利用側のツールやハンドラ |
src/private/*.ts |
tests/private/*.test.ts, セキュリティポリシーとの整合性 |
評価しないこと（自動化済み）
以下は CI・hooks・Lefthook が自動検出するため、Cursor で重複チェックしない:
- TypeScript 型エラー（
tsc --noEmit— PostToolUse hook + CI） - Oxlint 違反（PostToolUse hook + CI）
- Biome フォーマット（PostToolUse hook + CI）
new Date()の使用（banned-patterns — PostToolUse hook + CI）- テストの pass/fail（Stop hook + CI）
npm audit（security.yml — 週次 + PR）
評価する観点
1. content テキストの充足性
content[0].textに LLM が判断に必要なデータが含まれているか- ルールと NG/OK パターンは
.claude/rules/tools.mdの「content テキストにデータを含める」節を参照
2. セキュリティポリシー遵守
Private ツール（tools/private/, src/private/）の変更時に確認:
- 除外すべきフィールド・マスク対象・チェックリストは
.claude/rules/sensitive-data.mdを参照 - エラーメッセージ（catch ブロック）に認証情報やユーザー固有情報が混入していないか
3. アーキテクチャ整合性
CLAUDE.mdのアーキテクチャ節と.claude/rules/tools.mdのルールに準拠しているかserver.tsを直接編集していないか（ツール登録はtool-registry.ts経由）
4. テストの質
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.
- 3d ago First seen · 145 lines · 1,739 tokens per session scan A f0cd200695fe
cursorrules is a cursor rule published in the GitHub repository tjackiet/bitbank-lab-mcp (0 stars, last pushed today), licensed MIT. It adds 1,739 tokens to every session, about $0.0087 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to cursorrules, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.