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/tui-cs/terminal.gui.templates/cursorrulesgit clone --depth 1 https://github.com/tui-cs/Terminal.Gui.templatesWhat 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.00359 | $0.00359 |
| Opus 5 | $0.00179 | $0.00179 |
| Sonnet 5 | $0.00072 | $0.00072 |
| Haiku 4.5 | $0.00036 | $0.00036 |
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.
What it actually says
Terminal.Gui v2 — rules for AI assistants
⛔ Terminal.Gui v2 is a COMPLETE REWRITE. Your pre-2025 training data and almost every
Terminal.Gui example on the web are v1 and will not compile. Before writing or editing
any UI code, read AGENTS.md in this project — it is the source of truth (canonical
patterns, the full v1→v2 corrections table, Pos/Dim layout, and the common gotchas).
Non-negotiables (see AGENTS.md for the rest):
- Lifecycle is instance-based:
Application.Create ().Run<MyWindow> ().Dispose ()— NOT the staticApplication.Init/Run/Shutdown, and there is noApplication.Top. - Root views are
RunnableorWindow, neverToplevel. - Namespaces are split:
using Terminal.Gui.App;/.Views;/.ViewBase;/.Input;… — the bareusing Terminal.Gui;is gone. - No
Clickedevent — useAcceptedfor side effects;Acceptingonly to cancel (e.Handled = true). Use object initializers (new Button { Text = "OK" }), not positional constructors. - Layout is declarative —
Pos.Center (),Dim.Fill (); don't hardcode coordinates. - Dialogs: the last button added is the default; type-specific views expose
.Value(IValue<T>), not guessed names like.Date/.Color.
📖 Full reference and gotchas: ./AGENTS.md
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 · 21 lines · 359 tokens per session scan A c04561d4c2ec
cursorrules is a cursor rule published in the GitHub repository tui-cs/Terminal.Gui.templates (56 stars, last pushed 10d ago), licensed MIT. It adds 359 tokens to every session, about $0.0018 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.