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 commands/frankxai/agentic-creator-os/nextjs-deploygit 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/commands/frankxai/agentic-creator-os/nextjs-deploy)<a href="https://agentmods.dev/commands/frankxai/agentic-creator-os/nextjs-deploy"><img src="https://agentmods.dev/badge/commands/frankxai/agentic-creator-os/nextjs-deploy.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.00010 | $0.00383 |
| Opus 5 | $0.00005 | $0.00192 |
| Sonnet 5 | $0.00002 | $0.00077 |
| Haiku 4.5 | $0.00001 | $0.00038 |
Grade A, and why
nextjs-deploy 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 yesterday.
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.
What it actually says
Next.js Deployment Workflow Activated
You are now in Next.js Deployment Mode with Vercel integration ready.
MCP Servers for Deployment
Enable these as needed:
@next-devtools turn on- For pre-deployment checks and diagnostics@vercel turn on- For deployment operations (if configured)
Pre-Deployment Checklist
Before deploying, verify:
-
Build succeeds locally:
npm run build -
TypeScript compiles without errors:
npx tsc --noEmit -
Environment variables configured:
- Check
.env.localfor local development - Verify Vercel environment variables match
- Check
-
Database migrations applied (if using Supabase/Neon)
-
Test critical paths:
- Authentication flow
- API routes
- Database queries
Deployment Commands
Deploy to Vercel:
vercel # Preview deployment
vercel --prod # Production deployment
Check deployment status:
vercel ls # List deployments
vercel inspect [url] # Inspect specific deployment
Environment management:
vercel env ls # List environment variables
vercel env add [name] # Add new variable
Post-Deployment
-
Verify deployment:
- Check preview URL
- Test critical functionality
- Monitor error logs
-
Monitor performance:
- Check Vercel Analytics
- Review build logs
- Monitor error rates
Ready to Deploy
What would you like to deploy today?
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.
- yesterday First seen · 76 lines · 10 tokens per session scan A bce1ccc4d1a2
nextjs-deploy is a command published in the GitHub repository frankxai/agentic-creator-os (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 10 tokens to every session and 383 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-09-03.
Other commands, from other repositories
security-audit-static
Static security audit of AI-built code — map trust boundaries, cross-reference documented intent, self-refute every finding, and report only evidence-backed risks.
document-app
Reverse-engineer an AI-built codebase into the system documents reviewers and auditors need — a core set (architecture, flows, permissions, variables) plus conditional docs (emails, cron, SEO, automation) when they apply.
cloudflare-workers:debug
Interactive debugging workflow for Cloudflare Workers. Diagnoses deployment errors, runtime issues, and performance problems with step-by-step fixes.
cloudflare-kv:test
Test KV namespace connection and operations - validates configuration, performs CRUD tests, and reports diagnostics.
interview-summary
Summarize a customer interview transcript using JTBD analysis.
meta-synthesis
Detect cross-skill patterns and propose brain updates.