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/offorte/offorte-mcp-server/frontendgit clone --depth 1 https://github.com/offorte/offorte-mcp-serverWhat 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.00200 | $0.00200 |
| Opus 5 | $0.00100 | $0.00100 |
| Sonnet 5 | $0.00040 | $0.00040 |
| Haiku 4.5 | $0.00020 | $0.00020 |
Grade A, and why
frontend 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 yesterday.
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
Frontend & Javasccript
- Use Tailwind CSS for styling.
- Follow mobile-first responsive design.
- Avoid CSS-in-JS solutions (e.g., Emotion).
- When creating a frontend based on an uploaded image, be as close to the original as possible and double check the styling so it matches the image exactly.
- Use the installed dependencies over introducing something new.
- Use existing components from the (mono)repo.
- Use Prettier & Lint configurations from the (mono)repo to ensure consistent code style and best practices.
- For if statements, always use braces, even for single-line blocks.
- Use the installed dependencies over introducing something new.
Naming Conventions
- Directories/Files: Use lowercase with dashes (e.g., components/auth-wizard).
- Components: Favor named exports.
Package Manager
- Use PNPM
- Use fixed versions for dependencies
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.
- yesterday First seen · 23 lines · 200 tokens per session scan A 2cdbd6cda59f
frontend is a cursor rule published in the GitHub repository offorte/offorte-mcp-server (5 stars, last pushed 5mo ago), licensed MIT. It adds 200 tokens to every session, about $0.0010 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-31.
Other cursor rules, from other repositories
cursorrules
Kortix is a React Native + Expo app built with TypeScript, NativeWind (Tailwind CSS), and a custom design system.
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
android-viewmodel
Android ViewModel conventions — StateFlow, repository abstraction, coroutines, no LiveData.
project-structure
Cursor rule "project-structure" from HeeGyeong/ComposeSample, covering project structure guide, layer structure, modularization rules, dependency rules and resource management.
cursorrules
ROLE: Android Development Expert EXPERIENCELEVEL: Advanced (10+ years) SPECIALTIES.
ios-ui-development-focus
UI/UX and SwiftUI best practices - HIG compliance, presentation APIs, layout patterns.