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/sushaantu/boxentoWrote 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/sushaantu/boxento/component-patterns)<a href="https://agentmods.dev/rules/sushaantu/boxento/component-patterns"><img src="https://agentmods.dev/badge/rules/sushaantu/boxento/component-patterns/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/sushaantu/boxento/component-patterns"><img src="https://agentmods.dev/badge/rules/sushaantu/boxento/component-patterns.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.00174 | $0.00174 |
| Opus 5.5 | $0.00070 | $0.00070 |
| Sonnet 5.5 | $0.00035 | $0.00035 |
| Haiku 4.5 | $0.00017 | $0.00017 |
Grade A, and why
component-patterns 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.
What it actually says
- Use functional components with TypeScript
- Implement proper prop typing using interfaces
- Use Tailwind CSS for all styling needs
- Follow atomic design principles for component organization
- Implement proper error boundaries
- Use React hooks effectively
- Add appropriate accessibility attributes (aria-* props, role, etc.)
- Use compound components pattern for complex UI components
- Implement test coverage for all components
- Use memoization (React.memo, useMemo, useCallback) for performance optimization
- Create custom hooks for reusable logic
- Use Context API for state management that spans multiple components
- Implement lazy loading for components when beneficial
- Add proper keyboard navigation support
- Use composition over inheritance for component structure
- Add detailed JSDoc comments for component props
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 · 21 lines · 174 tokens per session scan A 70b4e8b0c7ce
component-patterns is a cursor rule published in the GitHub repository sushaantu/boxento (154 stars, last pushed 9d ago), licensed MIT. It adds 174 tokens to every session, about $0.0007 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-09-01.
Other cursor rules, from other repositories
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
rust
Rules for writing Rust services at PostHog. Focuses on writing async Rust with Tokio and encoding general Rust best practices from the Rust book and docs.
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
react-typescript
Rules for writing frontend code at PostHog (mostly React + Typescript with Kea).
ai-agent-specialist
Cursor rules for TypeScript, React, Node.js, clean architecture, testing, and WHY-oriented engineering guidance.
typescript-workflow
Cursor rule "typescript-workflow" from Adam-CAD/CADAM, covering typescript workflow rules, type checking, always run type check after type changes, type check commands and when to run type check.