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/madebyaris/poinf-of-salesWrote 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/madebyaris/poinf-of-sales/admin-interface-patterns)<a href="https://agentmods.dev/rules/madebyaris/poinf-of-sales/admin-interface-patterns"><img src="https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/admin-interface-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/madebyaris/poinf-of-sales/admin-interface-patterns"><img src="https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/admin-interface-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.00000 | $0.01195 |
| Opus 5 | $0.00000 | $0.00598 |
| Sonnet 5 | $0.00000 | $0.00239 |
| Haiku 4.5 | $0.00000 | $0.00120 |
Grade A, and why
admin-interface-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 9d 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 — 147 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Admin Interface Development Patterns
Admin Layout Structure
Component Organization
Admin components should follow this structure:
AdminLayout.tsx- Main admin wrapper with sidebar navigationAdmin[Section].tsx- Individual admin section components- Navigation integrated within single sidebar (no duplicate headers)
Navigation Pattern
// AdminLayout.tsx navigation structure
const adminSections = [
{ id: 'dashboard', label: 'Dashboard', icon: <LayoutDashboard /> },
{ id: 'pos', label: 'General POS', icon: <Store /> },
{ id: 'server', label: 'Server Interface', icon: <Users /> },
{ id: 'counter', label: 'Counter/Checkout', icon: <CreditCard /> },
{ id: 'kitchen', label: 'Kitchen Display', icon: <ChefHat /> },
{ id: 'settings', label: 'Settings', icon: <Settings /> },
{ id: 'staff', label: 'Manage Staff', icon: <UserCog /> },
{ id: 'menu', label: 'Manage Menu', icon: <Menu /> },
{ id: 'reports', label: 'View Reports', icon: <BarChart3 /> }
]
Sidebar Layout Best Practices
- Single Navigation Source: All navigation within sidebar, no duplicate top headers
- Collapsible Design: Support both expanded (w-64) and collapsed (w-16) states
- User Info Integration: User card and logout within navigation flow, not separate bottom section
- Flexible Layout: Use flexbox with spacer to push user info and logout to bottom
- Consistent Styling: Same button styles for all navigation items
User Authentication Integration
// User info within navigation
{!sidebarCollapsed && (
<div className="p-3 bg-muted/30 rounded-lg">
<div className="flex items-center gap-3">
<div className="w-8 h-8 bg-primary rounded-full flex items-center justify-center">
<User className="w-4 h-4 text-primary-foreground" />
</div>
<div className="flex-1 min-w-0">
<p className="text-sm font-medium truncate">{user.first_name} {user.last_name}</p>
<p className="text-xs text-muted-foreground truncate">{user.email}</p>
</div>
<Badge variant="outline">{user.role.toUpperCase()}</Badge>
</div>
</div>
)}
// Logout as navigation item
<Button
variant="ghost"
onClick={handleLogout}
className="w-full justify-start text-destructive hover:text-destructive hover:bg-destructive/10"
>
<LogOut className="w-5 h-5" />
{!sidebarCollapsed && <span className="ml-3">Logout</span>}
</Button>
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.
- 9d ago First seen · 147 lines · 1,195 tokens per session scan A 5dd07a34207b
admin-interface-patterns is a cursor rule published in the GitHub repository madebyaris/poinf-of-sales (140 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,195 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
mobile-design-system-and-structure
Mobile design system usage and folder structure.
mermaid-renderer-tooling
Renderização Mermaid canônica com vaults-diagram-tools.
cursorrules
คุณคือผู้ช่วยเขียนโค้ดผู้เชี่ยวชาญสำหรับโปรเจกต์ "Chonost Ecosystem" ภารกิจหลักคือช่วยสร้างเครื่องมือสร้างสรรค์ที่มี UX ไร้รอยต่อ.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.