A set of project rules for JavaScript or TypeScript code style. It requires ESLint to check code quality and Prettier to format code, and limits comments to cases where they explain something genuinely non-obvious.

Use it when preparing code for a pull request: run the project's lint and format commands, remove comments that merely repeat the code, and mark genuinely necessary explanations with their reason.

Formatting and linting catch mechanical problems before review, while unnecessary comments can become misleading as code changes. These rules make the expected checks and comment standards explicit.

How smekai/taskplanner configures Cursor

Reuse

Borrowing it

Nothing to install: this file belongs to smekai/taskplanner. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/smekai/taskplanner/main/.cursorrules

Clone the repo

git clone --depth 1 https://github.com/smekai/taskplanner

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/smekai/taskplanner/cursorrules/github.svg)](https://agentmods.dev/rules/smekai/taskplanner/cursorrules)

Your own site

<a href="https://agentmods.dev/rules/smekai/taskplanner/cursorrules"><img src="https://agentmods.dev/badge/rules/smekai/taskplanner/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/smekai/taskplanner/cursorrules"><img src="https://agentmods.dev/badge/rules/smekai/taskplanner/cursorrules.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,507 This file is loaded in full into every session.

When invoked 1,507 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original 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.

Model	Per session	Once invoked
Fable 5.1	$0.01507	$0.01507
Opus 5.5	$0.00603	$0.00603
Sonnet 5.5	$0.00301	$0.00301
Haiku 4.5	$0.00151	$0.00151

Measured 2d ago against content hash 51e643dd620c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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

.cursorrules · 137 lines

How it starts

The opening of the file, as written. The whole thing — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Code Style

ESLint and Prettier cover the mechanical part — run npm run lint and npm run format before a PR.

This is enforced. npm run lint runs scripts/check-comments.js, which fails on any comment in src/ and plugins/taskplanner/mod/src/; tests are exempt. Machine directives (eslint-disable, @ts-expect-error, prettier-ignore) are exempt. For the genuinely non-obvious case, prefix the comment with WHY: and give the reason — the check counts those and lets them through.

Beyond that: a comment is a signal that the code is not clear enough yet. Before writing one, try to make it unnecessary — name the function after the comment, extract the condition into a named predicate, split the branch out. Names and types stay true as the code changes; comments drift.

Do not write:

Comments that restate the code (// increment nextId).
Doc blocks on every exported symbol. A precise name and type already say it.
Section banners, decorative dividers, or step-by-step narration of a function body.
Rationale that belongs in the commit message, CHANGELOG.md, or a task's ### Plan.

Do write, sparingly:

A one-line note where the code must stay non-obvious: a workaround for an external bug, a deliberate deviation from an API contract, or an output format that must match byte-for-byte.

Comments belong in tests. A test name plus a short note explains the failure a case guards against far better than a comment sitting beside the code it guards.

If you find yourself explaining a function in prose, that is the signal to rewrite the function.

TaskPlanner — AI Agent Instructions

Tasks live as markdown under .tasks/. Prefer the MCP tools over hand-editing whenever they are available.

States

Backlog → BACKLOG.md
Next → NEXT.md
In Progress → IN_PROGRESS.md
Done → DONE.md
Rejected → REJECTED.md
Work Log → WORK_LOG.md (optional; not a task state)
Archived Done tasks may live under .tasks/archive/ when archiveDoneAfterDays is set — grep there before concluding a task never existed.

Read the full file on GitHub · 137 lines

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.

2d ago Changed · +8 tokens per session 51e643dd620c
20d ago Changed · +7 tokens per session 4d5a451c2cfe
1mo ago Changed · -59 lines · -709 tokens per session 4f8ab81d978c
2mo ago First seen · 196 lines · 2,201 tokens per session scan A feb2ac28f83a

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository smekai/taskplanner (23 stars, last pushed 2d ago), licensed MIT. It adds 1,507 tokens to every session, about $0.0060 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-08-30.

cursorrules next to 6 cursor rules from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
cursorrulessmekai/taskplanner	Cursor rule	23	2d ago	MIT	A	1,507	Cursor
ponytailDietrichGebert/ponytail	Cursor rule	185k	8d ago	MIT	A	604	Cursor
angular-20angular/angular	Cursor rule	101k	yesterday	MIT	A	0	Cursor
dev-standardapache/superset	Cursor rule	75k	today	Apache-2.0	A	1,147	Cursor
prefer-direct-imports-over-module-mocksprisma/orm	Cursor rule	48k	yesterday	Apache-2.0	A	0	Cursor
config-validation-and-normalizationprisma/orm	Cursor rule	48k	yesterday	Apache-2.0	A	0	Cursor
control-plane-descriptorsprisma/orm	Cursor rule	48k	yesterday	Apache-2.0	A	0	Cursor

taskplanner: Cursor rule for Cursor