What is frontend_overview_rules?

A set of rules describing the frontend structure of an application. The frontend is the part users see and interact with in a web browser, and the rules cover routes, reusable components, hooks, services, and shared types.

Use it when deciding where to add pages, feature components, shared components, authentication or chat hooks, API services, utilities, and shared type definitions.

It gives developers a common place and responsibility for each kind of frontend code. This reduces duplicated UI, misplaced API calls, and inconsistent dependency choices.

frontend_overview_rules — Cursor rule by ModelEngine-Group

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/modelengine-group/nexent/frontend_overview_rules

Clone the repo

git clone --depth 1 https://github.com/ModelEngine-Group/nexent

Made for: Cursor.

Per session 0 Nothing until a file matches its globs; then the whole rule loads.

When invoked 1,056 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.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.01056
Opus 5	$0.00000	$0.00528
Sonnet 5	$0.00000	$0.00211
Haiku 4.5	$0.00000	$0.00106

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

Security

Grade A, and why

frontend_overview_rules 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/frontend/frontend_overview_rules.mdc · 83 lines

How it starts

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