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/materialize-labs/ai-optimized-starter-appWrote 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/materialize-labs/ai-optimized-starter-app/auth)<a href="https://agentmods.dev/rules/materialize-labs/ai-optimized-starter-app/auth"><img src="https://agentmods.dev/badge/rules/materialize-labs/ai-optimized-starter-app/auth/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/materialize-labs/ai-optimized-starter-app/auth"><img src="https://agentmods.dev/badge/rules/materialize-labs/ai-optimized-starter-app/auth.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.00008 | $0.00910 |
| Opus 5.5 | $0.00003 | $0.00364 |
| Sonnet 5.5 | $0.00002 | $0.00182 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
auth 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 2mo 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 — 177 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Authentication Architecture
This document outlines our authentication approach using Clerk. Following these guidelines ensures consistent, secure user authentication throughout the application.
Core Principles
- Security First: Implement proper authentication checks for all protected resources
- Seamless Experience: Provide smooth authentication flows with minimal friction
- Consistent Patterns: Use standardized approaches for auth across the application
- Explicit Permissions: Make access controls clear and intentional
Clerk Integration
Our application uses Clerk for authentication, which provides:
- User management and authentication
- Social login providers
- Session management
- User profile management
- Security features like MFA
Server-Side Authentication
Importing Auth Helpers
Always use the correct imports for server components and server actions:
// In server components
import { auth } from "@clerk/nextjs/server"
// In middleware or other server contexts
import { getAuth } from "@clerk/nextjs/server"
Usage in Server Components
When accessing authentication in server components:
// app/dashboard/page.tsx
import { auth } from "@clerk/nextjs/server"
import { redirect } from "next/navigation"
export default async function DashboardPage() {
const { userId } = auth()
if (!userId) {
return redirect("/sign-in")
}
// Continue with authenticated page rendering
return (
<div>
<h1>Dashboard</h1>
{/* Dashboard content */}
</div>
)
}
Usage in Server Actions
When using authentication in server actions, always await the auth helper:
// actions/notes.ts
"use server"
import { auth } from "@clerk/nextjs/server"
import { db } from "@/db/db"
import { notesTable } from "@/db/schema/notes"
import { ActionState } from "@/types/server-action"
export async function createNote(
content: string
): Promise<ActionState<{ id: string }>> {
try {
// Get authenticated user
const { userId } = await auth()
if (!userId) {
return {
isSuccess: false,
message: "Authentication required"
}
}
// Create note for authenticated user
const [note] = await db.insert(notesTable)
.values({ content, userId })
.returning({ id: notesTable.id })
return {
isSuccess: true,
message: "Note created successfully",
data: { id: note.id }
}
} catch (error) {
console.error("Failed to create note:", error)
return {
isSuccess: false,
message: "Failed to create note"
}
}
}
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.
- 2mo ago First seen · 177 lines · 8 tokens per session scan A 754f97ddea98
auth is a cursor rule published in the GitHub repository materialize-labs/ai-optimized-starter-app (16 stars, last pushed 1y ago), licensed MIT. It adds 8 tokens to every session and 910 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
api-property-optionality-hygiene
Fix ApiProperty/ApiPropertyOptional optionality mismatches in DTO files; use for scheduled batch fixes or DTO edits.
python
Python best practices and patterns for modern software development with Flask and SQLite.
cursor
You are working on the checkout service. Preserve transaction integrity and auditability.
django
Definitive guidelines for writing maintainable, performant, and secure Django applications, emphasizing modern best practices, clear code organization, and efficient patterns.
server-state
USE WHEN: Fetching and caching server data with TanStack Query 5: queryOptions, hooks, mutations, invalidation.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.