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/ajgreyling/cursor-doctor/frontend-conventionsgit clone --depth 1 https://github.com/ajgreyling/cursor-doctorWrote 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/ajgreyling/cursor-doctor/frontend-conventions)<a href="https://agentmods.dev/rules/ajgreyling/cursor-doctor/frontend-conventions"><img src="https://agentmods.dev/badge/rules/ajgreyling/cursor-doctor/frontend-conventions.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00250 |
| Opus 5 | $0.00000 | $0.00125 |
| Sonnet 5 | $0.00000 | $0.00050 |
| Haiku 4.5 | $0.00000 | $0.00025 |
Grade A, and why
frontend-conventions 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 4d 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
Frontend Conventions (Docs UX)
This repository has no runtime web frontend. These conventions apply to documentation as the user interface.
Content layout
- Start with purpose and quick-start usage.
- Use short sections with clear headings.
- Prefer tables for file maps, commands, and schema summaries.
- Keep command examples copy-paste ready.
Language and tone
- Use concise, direct, task-first wording.
- Prefer active voice and present tense.
- Avoid redundant marketing language.
Examples and references
- Include practical command examples (
generate,audit,read). - Link related artifacts (
README, docs, rules, skills) to reduce navigation friction. - Keep one canonical source for each concern; reference instead of duplicating.
Accessibility in docs
- Use descriptive headings and meaningful link text.
- Avoid overly dense paragraphs; keep scan-friendly structure.
- Ensure code blocks include enough context to run safely.
Completeness checklist
- framework and stack
- layout/styling
- state management
- component patterns
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.
- 4d ago First seen · 42 lines · 0 tokens per session scan A f1ec30c94aa1
frontend-conventions is a cursor rule published in the GitHub repository ajgreyling/cursor-doctor (0 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 250 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
nativescript
NativeScript best practices and patterns for mobile applications.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
frontend-architecture
Vite + React SPA architecture - directory layout, providers, bundle splitting. Tailwind styling in tailwind.mdc.
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.