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/armanzeroeight/fastagent-pluginsWrote 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/armanzeroeight/fastagent-plugins/create-page)<a href="https://agentmods.dev/commands/armanzeroeight/fastagent-plugins/create-page"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/create-page/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/commands/armanzeroeight/fastagent-plugins/create-page"><img src="https://agentmods.dev/badge/commands/armanzeroeight/fastagent-plugins/create-page.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.00013 | $0.00814 |
| Opus 5.5 | $0.00005 | $0.00326 |
| Sonnet 5.5 | $0.00003 | $0.00163 |
| Haiku 4.5 | $0.00001 | $0.00081 |
Grade A, and why
create-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 1mo 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 — 132 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Page
Generate a new Next.js page with the appropriate rendering strategy.
Context
- Current directory: !
pwd - Next.js version: !
cat package.json | grep '"next"' || echo "Not found" - App Router: !
[ -d "app" ] && echo "Yes" || echo "No"
Your Task
Create a new Next.js page with proper structure and rendering strategy.
Arguments
$1: Page path (e.g., "products/[id]", "blog", "dashboard")$2: Optional flag for rendering strategy:--ssr: Server-Side Rendering--ssg: Static Site Generation--isr: Incremental Static Regeneration- (default: SSG for App Router, SSG for Pages Router)
Steps
-
Detect Next.js structure
- Check if using App Router (app/ directory) or Pages Router (pages/ directory)
- Determine Next.js version from package.json
-
Parse page path
- Extract route segments
- Identify dynamic segments ([id], [...slug])
- Determine if nested route
-
Create directory structure
- For App Router:
app/<path>/page.tsx - For Pages Router:
pages/<path>.tsxorpages/<path>/index.tsx - Create parent directories as needed
- For App Router:
-
Generate page component
For App Router:
- Server Component by default
- Add 'use client' if interactive
- Include metadata export
- Add loading.tsx and error.tsx if appropriate
For Pages Router:
- Add getStaticProps for SSG/ISR
- Add getServerSideProps for SSR
- Add getStaticPaths for dynamic routes
-
Add TypeScript types
- Props interface
- Params type for dynamic routes
- Metadata type for App Router
-
Provide usage instructions
- How to navigate to the page
- How to pass data
- How to customize rendering
- Next steps for implementation
Output Format
# Page Created: /<path>
## Files Created
- Page: app/<path>/page.tsx (or pages/<path>.tsx)
- Loading: app/<path>/loading.tsx (if App Router)
- Error: app/<path>/error.tsx (if App Router)
## Rendering Strategy
- Method: [SSG/SSR/ISR]
- Rationale: [Why this strategy was chosen]
## Usage
### Navigation
\`\`\`typescript
import Link from 'next/link';
<Link href="/<path>">Go to page</Link>
\`\`\`
### Data Fetching
[Instructions based on rendering strategy]
## Next Steps
1. Implement data fetching logic
2. Add UI components
3. Configure metadata/SEO
4. Test on development server
5. Optimize performance
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.
- 1mo ago First seen · 132 lines · 13 tokens per session scan A 04f9ac2e68f3
create-page is a command published in the GitHub repository armanzeroeight/fastagent-plugins (29 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 814 once invoked, about $0.0001 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-09-03.
Other commands, from other repositories
react-test
Enforce TDD workflow for React. Write React Testing Library tests first (behavior-focused, accessibility-first), then implement components. Detects Vitest or Jest and verifies coverage targets.
react-build
Fix React build failures (Vite, webpack, Next.js, CRA, Parcel, esbuild, Bun) incrementally — JSX/TSX compile errors, hydration mismatches, server/client component boundary failures, missing types. Invokes the react-build-resolver agent for minimal, surgical fixes.
react-review
Comprehensive React/JSX code review for hook correctness, render performance, server/client component boundaries, accessibility, and React-specific security. Invokes the react-reviewer agent (and typescript-reviewer alongside on TSX/JSX changes).
bundle-analyze
Tu es un expert performance React. Tu dois analyser la taille du bundle, identifier les dépendances volumineuses et proposer des optimisations.
aidd-churn
Rank files by hotspot score to identify prime candidates for refactoring before PR review.
trace-regression
Investigate a newly introduced bug or regression to identify the offending change and formulate a fix.