role-based-access-patterns

role-based-access-patterns is a cursor rule for Cursor from madebyaris/poinf-of-sales. It costs 0 tokens per session (1,612 once invoked), scanned A, original, MIT.

A set of role-based access control patterns for a point-of-sale system. Role-based access control means giving users access according to their job, such as administrator, manager, server, cashier, or kitchen staff.

In plain words
What is it for?
It is for defining roles, assigning their capabilities, routing them to the right screens, and controlling navigation for restaurant staff.
Why use it?
It prevents every user from seeing or changing every part of the system and keeps each interface focused on the user's responsibilities.

Cursor rule for Cursor

Written for Cursor: installed under .cursor/.

Good fit It is for defining roles, assigning their capabilities, routing them to the right screens, and controlling navigation for restaurant staff.

Compare 6 cursor rules from other repositories ↓
Install with agentmods
npx agentmods add rules/madebyaris/poinf-of-sales/role-based-access-patterns
Install

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.

Clone the repo
git clone --depth 1 https://github.com/madebyaris/poinf-of-sales

Made for: Cursor.

Wrote 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.

agentmods badge for role-based-access-patterns

README.md
[![agentmods](https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/role-based-access-patterns/github.svg)](https://agentmods.dev/rules/madebyaris/poinf-of-sales/role-based-access-patterns)
Your own site
<a href="https://agentmods.dev/rules/madebyaris/poinf-of-sales/role-based-access-patterns"><img src="https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/role-based-access-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.

agentmods 80×15 button for role-based-access-patterns

Your own site · 80×15
<a href="https://agentmods.dev/rules/madebyaris/poinf-of-sales/role-based-access-patterns"><img src="https://agentmods.dev/badge/rules/madebyaris/poinf-of-sales/role-based-access-patterns.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 1,612 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.01612
Opus 5 $0.00000 $0.00806
Sonnet 5 $0.00000 $0.00322
Haiku 4.5 $0.00000 $0.00161

Measured 11d ago against content hash 53c94b7a1bcf, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

role-based-access-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 11d 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.

.cursor/rules/role-based-access-patterns.mdc · 235 lines

How it starts

The opening of the file, as written. The whole thing — 235 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Role-Based Access Control (RBAC) Patterns

Role Definitions

Available Roles

type UserRole = 'admin' | 'manager' | 'server' | 'counter' | 'kitchen'

Role Capabilities

  • admin: Full system access, can switch to any interface
  • manager: Business operations, reports, staff oversight
  • server: Dine-in order creation only
  • counter: All order types + payment processing
  • kitchen: Order preparation and status updates

Frontend Role Routing

Main Router Pattern

// RoleBasedLayout.tsx
export function RoleBasedLayout({ user }: { user: User }) {
  // Admin gets AdminLayout with all interfaces
  if (user.role === 'admin') {
    return <AdminLayout user={user} />
  }
  
  // Other roles get specific interfaces
  switch (user.role) {
    case 'server': return <ServerInterface />
    case 'counter': return <CounterInterface />
    case 'kitchen': return <KitchenLayout user={user} />
    default: return <POSLayout user={user} />
  }
}

Navigation Access Control

// AdminLayout.tsx - Admin can access all interfaces
const adminSections = [
  { id: 'dashboard', label: 'Dashboard' },
  { id: 'pos', label: 'General POS' },        // Full POS access
  { id: 'server', label: 'Server Interface' }, // Server view
  { id: 'counter', label: 'Counter/Checkout' }, // Counter view
  { id: 'kitchen', label: 'Kitchen Display' }   // Kitchen view
  // + admin-only sections
]

Backend API Role Restrictions

Route Groups by Role

// routes.go pattern
func setupRoutes(router *gin.Engine) {
    api := router.Group("/api/v1")
    
    // Public routes
    api.POST("/auth/login", handlers.Login)
    
    // Protected routes
    protected := api.Group("", middleware.RequireAuth)
    
    // Admin only
    admin := protected.Group("/admin", middleware.RequireRole("admin"))
    admin.GET("/users", handlers.GetUsers)
    admin.POST("/users", handlers.CreateUser)
    
    // Server only
    server := protected.Group("/server", middleware.RequireRole("server"))
    server.POST("/orders", handlers.CreateDineInOrder) // Restricted to dine_in
    
    // Counter access
    counter := protected.Group("/counter", middleware.RequireRoles("counter", "admin"))
    counter.POST("/orders", handlers.CreateCounterOrder) // All order types
    counter.POST("/orders/:id/payments", handlers.ProcessPayment)
}

Read the full file on GitHub · 235 lines

Changes

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.

  1. 11d ago First seen · 235 lines · 1,612 tokens per session scan A 53c94b7a1bcf

Subscribe to this mod's changes

role-based-access-patterns is a cursor rule published in the GitHub repository madebyaris/poinf-of-sales (142 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,612 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.