Borrowing it
Nothing to install: this file belongs to nguyendat-lhd/notebypine-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/nguyendat-lhd/notebypine-mcp/main/.cursorrulesgit clone --depth 1 https://github.com/nguyendat-lhd/notebypine-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/nguyendat-lhd/notebypine-mcp/cursorrules)<a href="https://agentmods.dev/rules/nguyendat-lhd/notebypine-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/nguyendat-lhd/notebypine-mcp/cursorrules/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/nguyendat-lhd/notebypine-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/nguyendat-lhd/notebypine-mcp/cursorrules.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.01419 | $0.01419 |
| Opus 5.5 | $0.00568 | $0.00568 |
| Sonnet 5.5 | $0.00284 | $0.00284 |
| Haiku 4.5 | $0.00142 | $0.00142 |
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 2mo 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.
Notebypine MCP - Code Mode Rules
Primary Workflow: Code Mode Orchestration
When working with this codebase and MCP server, ALWAYS follow this pattern:
1. Tool Discovery First
- Use
agent/helpers/searchTools.tsto discover appropriate tools before calling them - Search with keywords like "incident", "solution", "export", "search" to find relevant tools
- Always check tool relevance scores and pick the highest-rated ones
2. Route Through Helper Stack
- NEVER call MCP tools directly - ALWAYS use
agent/helpers/callMCPTool.ts - Use
agent/helpers/router.tsfor automatic routing decisions - All calls should go through the wrapper functions, not direct MCP invocation
3. Security & Logging
- All logging is automatically redacted via
agent/helpers/redact.ts - Never log raw payloads or sensitive data
- Use sample-size logging (default 5-10 rows) for large datasets
- Enable verbose mode only when explicitly requested
4. Use Skills for Complex Workflows
- For log analysis: Use
agent/skills/triageFromLogfile.ts - For CSV exports: Use
agent/skills/saveSheetAsCSV.ts - For end-to-end workflows: Use
agent/examples/incident_to_kb.ts
Code Mode Best Practices
File Structure
agent/
├── helpers/ # Reusable orchestration helpers
├── servers/notebypine/ # Tool wrappers (one per tool)
├── skills/ # Reusable operational flows
└── examples/ # End-to-end demonstrations
Import Patterns
// ✅ GOOD: Route through helpers
import { callMCPTool } from '../helpers/callMCPTool.js';
import { searchTools } from '../helpers/searchTools.js';
import { routeCall } from '../helpers/router.js';
// ❌ AVOID: Direct MCP calls
// import { mcp } from '@modelcontextprotocol/sdk';
Typical Workflow
- Discovery:
searchTools("incident|solution|export") - Import: Import only required wrappers
- Execute: Use
callMCPTool()orrouteCall() - Log: Summaries are automatically logged (top 3 rows/items)
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.
- 2mo ago First seen · 170 lines · 1,419 tokens per session scan A e8752359edb4
cursorrules is a cursor rule published in the GitHub repository nguyendat-lhd/notebypine-mcp (0 stars, last pushed 12mo ago), licensed MIT. It adds 1,419 tokens to every session, about $0.0057 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-09-01.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .