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-page)<a href="https://agentmods.dev/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-page"><img src="https://agentmods.dev/badge/commands/larouexnonprofitconsulting/larouex-fullstack-plugin/add-page.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.00143 |
| Opus 5 | $0.00000 | $0.00072 |
| Sonnet 5 | $0.00000 | $0.00029 |
| Haiku 4.5 | $0.00000 | $0.00014 |
Grade A, and why
add-page 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 6d 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-page — 100% identical, 0 lines differ
What it actually says
Create a new Next.js page with proper routing and structure.
Generate:
- Page file in /app with proper naming for Next.js routing
- Layout wrapper with consistent structure
- TypeScript types for page props and params
- SEO metadata using Next.js 15 Metadata API (title, description, Open Graph)
- Responsive Bootstrap grid structure
- Server Component pattern for data fetching (if needed)
- Client Component patterns for interactivity (if needed)
- Loading state (loading.tsx) and error boundary (error.tsx)
- Page-specific styles if required
- Example content structure
Include proper type safety, accessibility attributes, and responsive design. Follow Next.js 15 App Router conventions and best practices.
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.
- 6d ago First seen · 16 lines · 0 tokens per session scan A 5401c5f0498c
add-page 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 143 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
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…
add-cms-ui
Create content management UI for editing static JSON content files. Build content editor forms with validation for JSON structure. Implement file upload functionality for JSON updates. Add preview functionality to see changes before publishing. Track version history of content changes with timestamps and authors.…
add-component
Create a reusable React component with TypeScript and best practices.
add-error-boundary
Implement React error boundaries throughout the application. Create error boundary component with componentDidCatch lifecycle. Add fallback UI with friendly error message and retry button. Log errors to monitoring service (Sentry, Azure Monitor) with stack traces. Implement granular boundaries for different sections…
add-form
Create a form component with validation and comprehensive functionality.
add-image-gallery
Create an image gallery component with upload capability. Implement responsive grid layout using Bootstrap grid system. Add lightbox modal for full-size image viewing with navigation controls. Create image upload interface with drag-and-drop and preview. Support multiple image uploads simultaneously. Implement lazy…