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/rm2thaddeus/pixel_detective/component-architecture-patternsgit clone --depth 1 https://github.com/rm2thaddeus/Pixel_DetectiveWhat 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.03613 |
| Opus 5 | $0.00000 | $0.01806 |
| Sonnet 5 | $0.00000 | $0.00723 |
| Haiku 4.5 | $0.00000 | $0.00361 |
Grade A, and why
component-architecture-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 2d 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 — 532 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Component Architecture Patterns
🏗️ COMPONENT DESIGN PATTERNS (From Sprint 10 Lessons)
Based on architectural review findings and real refactoring experiences during Sprint 10.
🚨 ANTI-PATTERN: "God Components" (Sprint 10 Discovery)
The Problem - Large Monolithic Components
// ❌ ANTI-PATTERN: 424-line HomePage component
export default function HomePage() {
// State management (50+ lines)
const [backendStatus, setBackendStatus] = useState<'loading' | 'ok' | 'error'>('loading')
const [setupStep, setSetupStep] = useState(1)
const [healthStatus, setHealthStatus] = useState<'loading' | 'ok' | 'error'>('loading')
// Color mode values (20+ lines)
const sidebarBg = useColorModeValue('white', 'gray.800')
const textColor = useColorModeValue('gray.800', 'white')
const mutedTextColor = useColorModeValue('gray.600', 'gray.300')
// ... 15+ more color definitions
// Effects and handlers (100+ lines)
useEffect(() => {
const checkBackendHealth = async () => {
// Complex health check logic
}
checkBackendHealth()
const interval = setInterval(checkBackendHealth, 30000)
return () => clearInterval(interval)
}, [])
// More effects...
useEffect(() => {
if (backendStatus === 'ok' && collection) {
setSetupStep(3)
} else if (backendStatus === 'ok') {
setSetupStep(2)
} else {
setSetupStep(1)
}
}, [backendStatus, collection])
// Complex render logic (200+ lines)
return (
<Box minH="100vh">
{/* Massive JSX structure */}
</Box>
)
}
Problems with this approach:
- Performance: Entire component re-renders on any state change
- Maintainability: Hard to understand and modify
- Testing: Difficult to test individual features
- Reusability: Logic tied to specific component
- Debugging: Hard to isolate issues
✅ SOLUTION: Component Composition Pattern
1. Extract Logical Sections
// ✅ PATTERN: Focused, single-responsibility components
export default function HomePage() {
return (
<Box minH="100vh">
<Header />
<Flex>
<SystemStatusSidebar />
<MainContent />
</Flex>
<CollectionModal />
<AddImagesModal />
</Box>
)
}
// ✅ Each component has a single responsibility
function SystemStatusSidebar() {
const { backendStatus, setupProgress } = useSystemHealth()
return (
<Sidebar>
<SetupProgress progress={setupProgress} />
<SystemStatus status={backendStatus} />
<CollectionStats />
</Sidebar>
)
}
function MainContent() {
const { setupStep } = useSystemHealth()
return (
<Container>
<HeroSection />
{setupStep >= 3 ? <FeaturedActions /> : <SetupGuidance />}
<AdditionalTools />
</Container>
)
}
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.
- 2d ago First seen · 532 lines · 0 tokens per session scan A d19ca5e498fa
component-architecture-patterns is a cursor rule published in the GitHub repository rm2thaddeus/Pixel_Detective (21 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,613 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-30.
Other cursor rules, from other repositories
modus-angular-icon-names
Complete list of valid Modus icon names for Angular applications.
oiloil-ui-ux-guide
Shared instructions for maintaining modern-ui-ux-review.
prototype-previewer
Build interactive prototype reviewers with synced review notes and Figma capture pages.
figma-performance
Handling large documents efficiently in the Plugin API.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.