Borrowing it
Nothing to install: this file belongs to bkotos/todoist-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/bkotos/todoist-mcp/master/.cursorrulesgit clone --depth 1 https://github.com/bkotos/todoist-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/bkotos/todoist-mcp/cursorrules)<a href="https://agentmods.dev/rules/bkotos/todoist-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/bkotos/todoist-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/bkotos/todoist-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/bkotos/todoist-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.01974 | $0.01974 |
| Opus 5.5 | $0.00790 | $0.00790 |
| Sonnet 5.5 | $0.00395 | $0.00395 |
| Haiku 4.5 | $0.00197 | $0.00197 |
Grade A, and why
cursorrules scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
if (axios.isAxiosError(error)) { How it starts
The opening of the file, as written. The whole thing — 316 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Todoist MCP Server - Development Standards
TDD Approach
ALWAYS write tests first:
- Red - Write a failing test
- PAUSE - Ask user to pause and read the tests before proceeding to green
- Green - Write minimal code to make it pass
- Refactor - Improve code while keeping tests green
Architecture
- Use functional programming approach with pure functions
- Separate concerns: client logic in
client.ts, business logic intodoist.ts - Use Vitest module mocking for testing (not dependency injection)
- Keep functions small and focused on single responsibility
Code Style
- Use 2 spaces for indentation (configured in .editorconfig)
- Prefer const over let, avoid var
- Use arrow functions for consistency
- Use template literals for string interpolation
- Use destructuring for cleaner code
Testing
-
Write tests first (TDD approach)
-
Use descriptive test names that explain the behavior
-
Mock modules at the top of test files with
vi.mock('./module') -
Import Vitest types only, not runtime functions:
// ✅ Good - import types only import type { MockedFunction, Mocked } from 'vitest'; // ❌ Bad - import runtime functions import { vi, describe, it, expect } from 'vitest'; -
Test both success and error cases
-
Keep tests focused and isolated
-
Tests are sufficient validation - do NOT start/run the project manually
-
Running
npm testis the only validation needed for new features -
Do NOT use
npm run dev,npx tsx src/index.ts, or any server startup commands -
Do NOT check server logs or verify server is running
-
Focus on test coverage and test results only
AAA Test Pattern
ALWAYS follow this exact structure:
it('should do something', async () => {
// arrange
const mockClient = {
get: vi.fn().mockResolvedValue({ data: mockData }),
};
mockGetTodoistClient.mockReturnValue(mockClient);
// act
const result = await functionName();
// assert
expect(result).toContain('expected output');
expect(mockClient.get).toHaveBeenCalledWith('/endpoint');
});
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 · 316 lines · 1,974 tokens per session scan A 97f3218042fc
cursorrules is a cursor rule published in the GitHub repository bkotos/todoist-mcp (0 stars, last pushed 10mo ago), licensed MIT. It adds 1,974 tokens to every session, about $0.0079 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
mcpnuke-tests
Test conventions for mcpnuke — enforces TDD workflow.
debug-issue
When the user reports a bug, an error, or unexpected behavior. Enforces four structured phases — reproduction, failing test, root cause isolation, fix and verify — to stop guess-and-check loops.
common-testing
Testing requirements: 80% coverage, TDD workflow.
testing_rules
A testing guide covering TDD, where tests are written before code, and BDD, where expected behavior is described in Given-When-Then form.
tdd
Test-driven development — red-green-refactor cycle.
testing-standards
testing guidelines and expectations.