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.
git clone --depth 1 https://github.com/BetterTyped/hype-stackWrote 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.
[](https://agentmods.dev/rules/bettertyped/hype-stack/frontend-features)<a href="https://agentmods.dev/rules/bettertyped/hype-stack/frontend-features"><img src="https://agentmods.dev/badge/rules/bettertyped/hype-stack/frontend-features/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/bettertyped/hype-stack/frontend-features"><img src="https://agentmods.dev/badge/rules/bettertyped/hype-stack/frontend-features.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.1 | $0.00000 | $0.00653 |
| Opus 5.5 | $0.00000 | $0.00261 |
| Sonnet 5.5 | $0.00000 | $0.00131 |
| Haiku 4.5 | $0.00000 | $0.00065 |
Grade A, and why
frontend-features 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 1mo 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 — 45 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Frontend Features
Applies to all client apps: apps/frontend, apps/admin, apps/mobile, and apps/extension.
When working in an app's src/features, organize code by vertical domain ownership using src/features/<domain>/modules/<feature>.
Read apps/frontend/src/features/README.md for the full feature guidelines before making structural changes.
- ALWAYS nest feature code inside
<domain>/modules/<feature>/. Never place files directly insidesrc/features/<domain>/, and never use a flatsrc/features/<domain>/<feature>/without themodules/layer. Even a single-file feature gets its own module folder:src/features/settings/modules/profile-tab/profile-tab.tsx, notsrc/features/settings/profile-tab/profile-tab.tsx. - Pages belong in
src/routes/, NOT in features. Route files import feature components and render them. Features never contain "page" files. - Keep module-specific components, hooks, queries, schemas, types, utils, tests, and assets inside the owning
modules/<feature>/folder (for examplemodules/<feature>/components/,modules/<feature>/hooks/). - Hooks are scoped to where they're needed: module-level in
modules/<feature>/hooks/when only that module uses them, domain-level in<domain>/hooks/when shared across modules in the domain (for examplefeatures/auth/hooks/use-auth.ts), global insrc/hooks/when truly app-wide. - No flat files at the domain level except domain-scoped shared folders (
hooks/,listeners/,types/,constants/,utils/,store/). - Do not add new features as flat
src/features/<feature>orsrc/features/<domain>/<feature>folders. Always nest them undermodules/. - Do not move feature code into global
components,hooks,utils, ortypesfolders just because of file kind. - Import another feature through its public root API when available. Avoid deep imports into another feature's internals.
- Add new shared code only when there is a real shared owner. Otherwise keep it colocated with the module that needs it.
- Preserve and update feature root exports when changing public behavior.
- Run the most targeted available checks for the affected feature, then broaden checks when changes cross feature boundaries.
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.
- 1mo ago First seen · 45 lines · 0 tokens per session scan A 94df680c3636
frontend-features is a cursor rule published in the GitHub repository BetterTyped/hype-stack (12 stars, last pushed 15d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 653 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-31.
Other cursor rules, from other repositories
windsurfrules
Create detailed components with these requirements.
backend
Backend development rules for TT Studio - AI model management backend.
tanstack-start-guide
TanStack Start best practices emphasizing client-first architecture, type safety, and modern React patterns.
new-component
Workflow for creating new React components.
tanstack-react-router_routing
TanStack Router: Routing.
project-structure
Folder layout for Next.js App Router and Vite + React variants.