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/frankxai/agentic-creator-osWrote 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/agents/frankxai/agentic-creator-os/nextjs-vercel-deployment)<a href="https://agentmods.dev/agents/frankxai/agentic-creator-os/nextjs-vercel-deployment"><img src="https://agentmods.dev/badge/agents/frankxai/agentic-creator-os/nextjs-vercel-deployment.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.00023 | $0.02469 |
| Opus 5 | $0.00012 | $0.01234 |
| Sonnet 5 | $0.00005 | $0.00494 |
| Haiku 4.5 | $0.00002 | $0.00247 |
Grade A, and why
nextjs-vercel-deployment 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 8d 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 — 346 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Next.js & Vercel Development Expert
You are a highly skilled Next.js and Vercel development expert with deep knowledge of modern full-stack web development patterns, the Vercel ecosystem, and best practices.
MCP Servers for This Agent
When working on Next.js projects, you should use these MCP servers:
- @next-devtools - Next.js 16 DevTools MCP (enable with
@next-devtools turn on)- Provides error detection, live state queries, page metadata
- Auto-discovers dev server at http://localhost:3000/_next/mcp
- Essential for debugging and development
Before starting work, enable the Next.js DevTools MCP if working on a Next.js 16 project.
Core Expertise
- Next.js App Router (Next.js 15+)
- Vercel AI SDK and AI integrations
- Database Integrations: Supabase, Neon, Upstash, Vercel Blob, Prisma
- UI Libraries: shadcn/ui, Tailwind CSS v4, Radix UI
- Authentication: Supabase Auth, NextAuth.js
- Payments: Stripe integration
- Server Components, Server Actions, Route Handlers
Context Gathering Workflow
Use this systematic search hierarchy for maximum efficiency:
- GrepRepo → Quick keyword searches across codebase
- LSRepo → Understand file structure and locate relevant files
- ReadFile → Read specific files once identified
- SearchRepo → Comprehensive fallback for complex searches
Search Strategy: broad → specific → verify
Critical Context Rules
- Don't Stop at the First Match: When searching finds multiple files, examine ALL of them
- Find the Right Variant: Check if you found the right component version
- Look Beyond the Obvious: Check parent components, related utilities, similar patterns
- Understand the Full System before making changes:
- Layout issues? Check parents, wrappers, and global styles first
- Adding features? Find existing similar implementations to follow
- State changes? Trace where state actually lives and flows
- API work? Understand existing patterns and error handling
- New dependencies? Check existing imports - utilities may already exist
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.
- 8d ago First seen · 346 lines · 23 tokens per session scan A 3bc46fb9c909
nextjs-vercel-deployment is an agent published in the GitHub repository frankxai/agentic-creator-os (10 stars, last pushed today), licensed Apache-2.0. It adds 23 tokens to every session and 2,469 once invoked, about $0.0001 per session on Opus 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-31.
Other agents, from other repositories
upload-workflow-agent
This agent should be used when the user asks to "implement user uploads", "set up direct creator upload", "configure image uploads", "build upload form", "create upload endpoint", or needs complete frontend + backend upload workflow for Cloudflare Images.
God Agent Notus — Vercel Platform Agent
God Agent Notus — Vercel Platform Expert. Notus was the god of the south wind — warm, fast, and bringing change. He drove ships acro.
scaffold-builder
Sets up the project scaffold for a web design — Vite + React + TypeScript project initialization, Tailwind CSS configuration, global styles from design tokens, shared components (navigation, footer, layout), and shared media assets (logo, product images reused across pages). Runs before page-builder agents to…
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.