cli

Coding rules for a TypeScript command-line program named Donut, including its folders, exports, interface code, and tests.

In plain words
What is it for?
Use them when changing the CLI, its Ink terminal interface, commands, shared UI pieces, session history, or Vitest tests.
Why use it?
They give contributors a consistent structure and discourage exposing internal helpers or adding unnecessary public code.

Cursor rule for Cursor

Install

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.

agentmods
npx agentmods add rules/nerds-odd-e/doughnut/cli
Clone the repo
git clone --depth 1 https://github.com/nerds-odd-e/doughnut

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,675 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03675
Opus 5 $0.00000 $0.01837
Sonnet 5 $0.00000 $0.00735
Haiku 4.5 $0.00000 $0.00367

Measured 2d ago against content hash a2160cebf4ea, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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

.cursor/rules/cli.mdc · 113 lines

How it starts

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

donut-cli

TypeScript CLI for Donut. Lives in cli/.

Structure

cli/
  src/                 # Production code: `main`/`run`, `nonInteractiveCli`, `interactiveInkSession` (TTY → Ink edge), Ink app, `commands/`
  src/commonUIComponents/  # Context-neutral Ink UI reused across stages and the main prompt (borders, guidance lists, y/n, past user block, stage key context)
  src/sessionScrollback/  # One Ink `<Static>` session history above the live column; transcript factories + recall answered rows; append context for stages
  src/commands/        # Slash-command and subcommand implementations + aggregated help
  src/shims/           # Modules referenced only from the esbuild `bundle` script (aliases)
  tests/               # Vitest unit tests (*.test.ts)
  vitest.config.ts
  tsconfig.json
  package.json

TypeScript module exports

Keep each module’s public surface small: export only what other modules actually use. Prefer leaving helpers, constants, and types unexported when they are implementation details. Do not add exports “for tests” or “maybe later” — if only tests need a symbol, test through a stable-boundary entry point when possible (unit-testing.mdc; see Vitest: observable behavior below). Avoid widening the export list when a single import site could instead live next to the code.

Commands

Task Command
Build bundle pnpm cli:bundle
Run tests pnpm cli:test
Mutation test (Stryker) CURSOR_DEV=true nix develop -c bash -c 'cd cli && pnpm test:mutation' — see the mutation-testing skill
Format pnpm cli:format
Lint pnpm cli:lint

Architecture notes

CLI architecture guidance lives in this rule and in cli/ code layout. New planning artifacts go under .planning/phases/ or .planning/quick/ — see gsd-coexistence.mdc.

Apply architectural changes when a feature needs them; challenge the fit first.

Session scrollback (interactive) — Past session lines use one Ink <Static> (append-only) above the live column (stage + MainInteractivePrompt). Generic SessionScrollback stays domain-agnostic; shell transcript shapes live in interactiveCliTranscript.tsx; recall “answered” outcomes use recallAnsweredScrollback.tsx; stages append via sessionScrollbackAppendContext.

Read the full file on GitHub · 113 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.

  1. 2d ago First seen · 113 lines · 0 tokens per session scan A a2160cebf4ea

Subscribe to this mod's changes

cli is a cursor rule published in the GitHub repository nerds-odd-e/doughnut (49 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,675 tokens. 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.