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/chihebnabil/lovable-boilerplateWrote 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/chihebnabil/lovable-boilerplate/quality)<a href="https://agentmods.dev/rules/chihebnabil/lovable-boilerplate/quality"><img src="https://agentmods.dev/badge/rules/chihebnabil/lovable-boilerplate/quality/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/chihebnabil/lovable-boilerplate/quality"><img src="https://agentmods.dev/badge/rules/chihebnabil/lovable-boilerplate/quality.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.00011 | $0.00684 |
| Opus 5.5 | $0.00004 | $0.00274 |
| Sonnet 5.5 | $0.00002 | $0.00137 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
quality 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Quality Checklist Rules
Pre-Ship Quality Gates
Code Architecture Quality
- No monolithic components - Each component under 300 lines with single responsibility
- Logic extraction - Reusable logic moved to custom hooks, not duplicated
- Type safety - Shared interfaces defined in
lib/types.tsand reused - Service layer - API calls abstracted to service functions, not inline
- Proper imports - Using path aliases (@/) and organized import groups
- Validation schemas - Zod schemas shared and reused across components
- Component composition - Complex UI built from smaller, focused components
Design Quality
- Uses intentional color palette that serves the design purpose
- Has proper visual hierarchy with varied typography scales
- Includes subtle animations and micro-interactions
- Features generous whitespace and purposeful spacing
- All interactive elements have clear hover/active states
- Accessibility standards are met (proper contrast, focus states)
- Mobile experience is thoughtfully designed
- Maintains cohesive visual story throughout
- Design feels custom-crafted, not template-like
- Visual identity matches target industry and audience
- Color choices enhance user experience and brand message
Essential Commands Check
npm run lint # MUST pass before shipping
npm run build # MUST succeed without errors
NEVER Ship Code That:
- Contains components over 300 lines mixing multiple concerns
- Has duplicated logic that could be extracted to hooks
- Uses inline API calls instead of service layer
- Lacks proper TypeScript interfaces
- Has accessibility contrast violations
- Contains copy-pasted code blocks
- Mixes business logic with presentation layer
- Has console errors or warnings
- Fails ESLint checks
Development Workflow
- Run
npm run devto start development - Follow component size limits (300 lines max)
- Extract reusable logic to hooks
- Test responsive design on mobile/desktop
- Verify accessibility contrast ratios
- Run
npm run lintand fix all issues - Ensure no console errors before shipping
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 · 95 lines · 11 tokens per session scan A 4811285e2fca
quality is a cursor rule published in the GitHub repository chihebnabil/lovable-boilerplate (65 stars, last pushed 3mo ago), licensed MIT. It adds 11 tokens to every session and 684 once invoked, about $0.0000 per session on Opus 5.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-30.
Other cursor rules, from other repositories
techdebt
Find and eliminate technical debt across the whole codebase — duplicated code, dead code, redundant abstractions.
mcp
Guidelines for implementing and interacting with the Task Master MCP Server.
new_features
Guidelines for integrating new features into the Task Master CLI.
utilities
// ✅ DO: Create focused, reusable utilities /.
commands
Guidelines for implementing CLI commands using Commander.js.
git_workflow
Git workflow integrated with Task Master for feature development and collaboration.