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/nerds-odd-e/doughnut/linting_formatinggit clone --depth 1 https://github.com/nerds-odd-e/doughnutWhat 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.00050 | $0.02435 |
| Opus 5 | $0.00025 | $0.01218 |
| Sonnet 5 | $0.00010 | $0.00487 |
| Haiku 4.5 | $0.00005 | $0.00244 |
Grade A, and why
linting_formating 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.
How it starts
The opening of the file, as written. The whole thing — 174 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Linting and Formatting in Donut Project
When to Use This Rule
Use this rule when:
- Fixing linting or formatting errors
- Running code quality checks
- Validating OpenAPI specifications
- Formatting code before committing
- Troubleshooting linting failures
- Working with Biome, Redocly, or backend linting
Overview
This project uses multiple linting tools to ensure code quality:
- Biome: Frontend, CLI, MCP server,
packages/donut-test-fixtures, Cypress, and other root-level TypeScript/JavaScript code - Redocly CLI: OpenAPI specification validation
- Backend linting: Java code quality checks (via Gradle)
Linting Philosophy
IMPORTANT: Linting is primarily for CI/CD validation. Developers should use format:all instead of lint:all during development, as formatting also fixes most linting issues automatically.
Running Linting
Run commands from the repo root through Nix.
Lint All Code
CURSOR_DEV=true nix develop -c pnpm lint:all
This runs:
- Backend Java linting (
pnpm backend:lint) - Frontend TypeScript/Vue linting (
pnpm frontend:lint) - CLI TypeScript linting (
pnpm cli:lint) - Shared API test fixtures (
packages/donut-test-fixtures) via Biome (pnpm test-fixtures:lint) - Cypress E2E test linting (
pnpm cy:lint) - OpenAPI specification linting (
pnpm openapi:lint)
Individual Linting Commands
pnpm backend:lint- Java code lintingpnpm frontend:lint- Frontend TypeScript/Vue lintingpnpm cli:lint- CLI TypeScript lintingpnpm test-fixtures:lint- Biome onpackages/donut-test-fixturesonlypnpm cy:lint- Cypress E2E test lintingpnpm openapi:lint- OpenAPI spec validation
Format vs Lint
- Use
CURSOR_DEV=true nix develop -c pnpm format:allduring development — it lints and auto-fixes (Biomecheck --write, Spotless apply,vue-tsc). Do not also runlint:all. Slice wrap-up does not runformat:allbefore the first commit;scripts/git-hooks/pre-commitrunsformat:changed. Run format only if that commit fails. - Use
CURSOR_DEV=true nix develop -c pnpm lint:allfor CI/CD validation only — it checks without fixing (plus a few script unit tests that format does not run).
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 First seen · 174 lines · 50 tokens per session scan A 01a0db747814
linting_formating is a cursor rule published in the GitHub repository nerds-odd-e/doughnut (49 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 2,435 once invoked, about $0.0003 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-30.
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.