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/LarouexNonprofitConsulting/larouex-fullstack-pluginWrote 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/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-protected-route)<a href="https://agentmods.dev/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-protected-route"><img src="https://agentmods.dev/badge/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-protected-route.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.1 | $0.00000 | $0.00135 |
| Opus 5 | $0.00000 | $0.00068 |
| Sonnet 5 | $0.00000 | $0.00027 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
add-protected-route 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 7d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- add-protected-route — 100% identical, 0 lines differ
What it actually says
Create a protected Next.js route with authentication enforcement.
Generate:
- Protected page component with authentication check
- Middleware for route protection (middleware.ts pattern)
- Authentication state verification (server-side)
- Redirect logic to login page with return URL
- Loading state while checking authentication
- Unauthorized access handling
- TypeScript types for protected route props
- Higher-order component or wrapper for route protection
- API route protection with authentication middleware
- Role-based access control (RBAC) if needed
Implement both page-level protection (Server Components) and API route protection. Include proper error handling, loading states, and redirect logic. Ensure protected routes work with SSR and Client Components.
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.
- 7d ago First seen · 16 lines · 0 tokens per session scan A b11adf349cc8
add-protected-route is a command published in the GitHub repository LarouexNonprofitConsulting/larouex-fullstack-plugin (8 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 135 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-31.
Other commands, from other repositories
audit-accessibility
Audit the project for WCAG 2.1 AA accessibility compliance.
scaffold-azure-full
Create a complete Azure full-stack application with modern architecture.
scaffold-azure-nextjs
Scaffold a new Next.js 15 project optimized for Azure Static Web Apps deployment.
add-analytics-google
Integrate Google Analytics 4 for comprehensive tracking. Install gtag.js script in application layout. Create analytics wrapper hooks for type-safe event tracking. Implement automatic pageview tracking with Next.js router events. Add custom event tracking for business metrics: button clicks, form submissions…
add-caching
Implement comprehensive caching strategy across the application. Configure CDN caching headers in staticwebapp.config.json or Railway configuration. Set cache-control headers for static assets (immutable for hashed files). Implement static generation with revalidation using Next.js ISR. Add client-side caching with…
add-checkout
Create comprehensive shopping cart and checkout flow. Implement cart state management with Context API or Zustand. Create cart UI component with item list, quantity controls, and remove buttons. Calculate totals including subtotal, tax, shipping, and discounts. Add shipping address form with validation. Implement…