finesse-brief

finesse-brief is a cursor rule for Cursor from mouse-lin/finesse-brief. It costs 0 tokens per session (16,905 once invoked), scanned A, original, MIT.

A product-definition method that creates a written workbench specification before anyone builds the interface. A workbench can be a personal browser page for daily records or a larger browser system with modules, pages, and data entities.

In plain words
What is it for?
Use it to plan personal tracking pages or systems such as customer-management tools, enterprise systems, AI-agent consoles, dashboards, and smart-factory software.
Why use it?
It clarifies what the product is, what its first screen should say, and which data supports that message. This helps builders create a page that remains useful after the first visit.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/. Also seen: names the AskUserQuestion tool; mentions Claude Code.

Good fit Use it to plan personal tracking pages or systems such as customer-management…

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/mouse-lin/finesse-brief/finesse-brief
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.

Clone the repo
git clone --depth 1 https://github.com/mouse-lin/finesse-brief

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.

agentmods badge for finesse-brief

README.md
[![agentmods](https://agentmods.dev/badge/rules/mouse-lin/finesse-brief/finesse-brief.svg)](https://agentmods.dev/rules/mouse-lin/finesse-brief/finesse-brief)
Your own site
<a href="https://agentmods.dev/rules/mouse-lin/finesse-brief/finesse-brief"><img src="https://agentmods.dev/badge/rules/mouse-lin/finesse-brief/finesse-brief.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 16,905 The whole file, excluding the scripts and references it only reads on demand.
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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.16905
Opus 5 $0.00000 $0.08453
Sonnet 5 $0.00000 $0.03381
Haiku 4.5 $0.00000 $0.01690

Measured 7d ago against content hash 0b084bfac317, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

finesse-brief 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 7d 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/finesse-brief.mdc · 658 lines

How it starts

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

finesse-brief — The Workbench Architect

This skill runs one step upstream of every UI skill. It answers what is this thing — the identity, the modules, the sentence at the top of the first screen, the data that makes that sentence true, and the entities underneath it all. It never writes an interface. Its only deliverable is .workbench/spec.md — a self-contained brief that finesse-ui reads mechanically and that any other builder (Cursor, v0, 通义, a person) can read too, because the spec carries its own decoder (§8). Where there's no filesystem, it prints that spec in one copyable block instead.

The thing being defined is a web page. An H5 page opened in a phone browser, or a console opened in a desktop browser. Not a native app — no push notifications, no badges, no app store, no background jobs of its own. That constraint is not a footnote, it is the reason this method exists: a web page has no push to fall back on, so the only thing that brings someone back tomorrow is that the page had something to say today. In an app a mediocre hook is rescued by a notification. Here nothing rescues it.

Two domains, one method.

  • 个人域 (personal) — one person, one life domain, opened on a rhythm. 「小暖的姨妈工作台」「阿力的增肌工作台」「毛孩子工作台」. He feeds it, it tells him something he didn't already know.
  • 系统域 (system) — a workbench built around a business object, with modules, page depth and a real data model. CRM · ERP · AI Agent 控制台 · 数据看板 · 智慧工厂 · 项目管理 · 电商后台 · 内容创作中心 · 教务 · 医疗 · 运营后台. Several kinds of people may look at it; much of its data is written by systems rather than by hand.

They share the five parts (§2), the structure taxonomy (§5) and — above all — the data floor (§3), which is the one gate that is never skipped in either domain. They differ in depth: a personal workbench is a rail of channels over a handful of fields; a system workbench is a set of modules, each with a page tree and entities under it (§8.B).

Two failures own this category, and they are not symmetric. The visible one is never starting — the user wants a workbench and can't name one, so nothing gets built. The expensive one is building the wrong one beautifully: a gorgeous page whose top line reads 今天是黄体期第 3 天 on day one and reads the same thing forever, or a gorgeous admin console whose twelve tables are all empty the day it meets a real database — because in both cases nobody asked where the numbers come from. This skill's entire job is to kill the second one before the first line of code.

Every rule below is contextual. Read the situation first, set the structure, then pull only what fits. A skill that produces the same workbench for every user has failed.


Read the full file on GitHub · 658 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. 7d ago First seen · 658 lines · 0 tokens per session scan A 0b084bfac317

Subscribe to this mod's changes

finesse-brief is a cursor rule published in the GitHub repository mouse-lin/finesse-brief (47 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 16,905 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.