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/golid-ai/golid/solidstart-routinggit clone --depth 1 https://github.com/golid-ai/golidWrote 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/golid-ai/golid/solidstart-routing)<a href="https://agentmods.dev/rules/golid-ai/golid/solidstart-routing"><img src="https://agentmods.dev/badge/rules/golid-ai/golid/solidstart-routing.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00694 |
| Opus 5 | $0.00000 | $0.00347 |
| Sonnet 5 | $0.00000 | $0.00139 |
| Haiku 4.5 | $0.00000 | $0.00069 |
Grade A, and why
solidstart-routing 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 5d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SolidStart Routing and Layout Boundaries
Thesis: Route groups
(private)and(public)organize auth boundaries without adding URL segments. Layout files andPRIVATE_ROUTESmust stay in sync so SSR and SPA navigation agree.
Reference files: frontend/src/routes/(private).tsx,
frontend/src/routes/(public).tsx, frontend/src/lib/constants.ts,
frontend/src/app.tsx, navigation components under frontend/src/components/organisms/navigation/.
Route Groups Do Not Change URLs
SolidStart groups like (private) and (public) are path-transparent.
Files under frontend/src/routes/(private)/dashboard/index.tsx serve /dashboard,
not /(private)/dashboard.
// Layout boundary — auth required
frontend/src/routes/(private).tsx
// Page — URL is /dashboard
frontend/src/routes/(private)/dashboard/index.tsx
// Public auth pages — URL is /login
frontend/src/routes/(public)/login/index.tsx
Do not duplicate the same URL under both groups. One route file owns each path.
Private vs Public Layouts
(public).tsx— no auth required. Landing (/) is full-bleed; auth pages use constrained width.(private).tsx— auth required. SSR middleware redirects unauthenticated users; client-side effect in the layout is a safety net for SPA navigation.
When adding a protected page:
- Place it under
frontend/src/routes/(private)/. - Add the path to
PRIVATE_ROUTESinfrontend/src/lib/constants.ts— SSR auth redirects won't work without this. - Use
redirectTo(notreturn,next, orredirect) for login redirects.
Audit The Whole Shell
app.tsx root layout wraps every route. When changing auth or navigation:
- Navbar links and active states
- Sidebar visibility (private routes only)
- Footer variants
- Root layout spacing tied to private-route detection
A page can render correctly while global chrome still shows wrong links or sidebar state for the route group.
Auth Guards in Layout vs Page
- Layout-level:
(private).tsxblocks unauthenticated access to all child routes. - Page-level: role or resource checks (e.g., admin-only) belong in the page
component. Prefer
<Show when={...} fallback={...}>over early returns before reactive setup — early returns skip signal creation and break re-renders when async guards later pass.
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.
- 5d ago First seen · 80 lines · 0 tokens per session scan A e6626199afc6
solidstart-routing is a cursor rule published in the GitHub repository golid-ai/golid (40 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 694 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
adapter-features
Database-specific features must be implemented in the specialized adapter only. Base adapters (postgres, mysql, etc.) must remain database-agnostic.
unit-tests-tdd
TDD required for behavior changes; ≥80% package coverage on touched packages; unit-test conventions.
integration-tests
Human-readable integration test requests; helpers vs httptest; suites/ vs per-DB placement.
state-management
Use the following stack. Do not introduce or recommend Redux or React Context for shared/global state.
backend
You are an expert in Go, Gin, Gorm, Gen, Cosy (https://cosy.uozi.org/) with a deep understanding of best practices and performance optimization techniques in these technologies.
core
Core token-efficiency and response discipline rules. Always active.