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 skills/darellchua2/opencode-config-template/amplify-nextjs-deployment-skillnpx skills add darellchua2/opencode-config-template --skill amplify-nextjs-deployment-skillgit clone --depth 1 https://github.com/darellchua2/opencode-config-templateWrote 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/skills/darellchua2/opencode-config-template/amplify-nextjs-deployment-skill)<a href="https://agentmods.dev/skills/darellchua2/opencode-config-template/amplify-nextjs-deployment-skill"><img src="https://agentmods.dev/badge/skills/darellchua2/opencode-config-template/amplify-nextjs-deployment-skill.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.00046 | $0.03531 |
| Opus 5 | $0.00023 | $0.01766 |
| Sonnet 5 | $0.00009 | $0.00706 |
| Haiku 4.5 | $0.00005 | $0.00353 |
Grade A, and why
amplify-nextjs-deployment-skill scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
For custom domains, transfer DNS to Route53 **first**, then associate the domain with Amplify. Wildcard subdomains may show `verified: False` in Amplify console even when the domain is actually working — verify with `cur How it starts
The opening of the file, as written. The whole thing — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
What this skill does
- Documents the 7 production-learned gotchas for deploying Next.js 16+ to AWS Amplify Hosting
- Provides a canonical
amplify.ymlbuild spec template with SSR Lambda env-var injection - Covers GitHub Actions-based deploy triggers (more reliable than Amplify webhooks)
- Includes post-deploy verification commands and rollback strategy
- Provides a troubleshooting matrix mapping symptoms → root causes → fixes
When to use me
- When the user mentions "Amplify", "amplify.yml", "SSR Lambda", "CloudFront OAC", or "deploy to Amplify"
- When debugging
process.env.*returningundefinedin Next.js Server Components after a successful Amplify build - When setting up a new Next.js + Amplify Hosting deployment
- When configuring custom domains via Route53 + Amplify
- When deploying media/S3 + CloudFront integration with Next.js Image optimization
- When reviewing or writing
amplify.yml, deploy workflows, or infra-as-code for Amplify
Prerequisites
- Next.js 16+ project (App Router + Turbopack build)
- AWS account with Amplify Hosting enabled
- (Optional) OpenTofu/Terraform infra module for S3 + CloudFront + Route53
- (Optional) GitHub Actions workflow for
aws amplify start-jobdeploy triggers
The 7 Critical Rules (Production-Learned)
These rules come from production debugging. Violating any of them typically produces a successful build pipeline with a broken runtime — the hardest failure mode to detect.
Rule 1: Amplify branch env vars are build-time ONLY
The Amplify SSR Lambda does NOT receive branch env vars at runtime. Next.js Turbopack inlines process.env.* at build time from .env.production. The amplify.yml build spec MUST inject env vars into .env.production so they're baked into the server bundle.
Symptom if violated: process.env.DATABASE_URL is undefined in Server Components, despite the build succeeding and the env var being set in Amplify console.
Fix: See amplify.yml template below — the preBuild phase writes env vars to .env.production.
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 · 317 lines · 46 tokens per session scan A 91505bf179b2
amplify-nextjs-deployment-skill is a skill published in the GitHub repository darellchua2/opencode-config-template (6 stars, last pushed 4d ago), licensed Apache-2.0. It adds 46 tokens to every session and 3,531 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…
gke-reliability
Improves GKE workload reliability, using PDBs, health probes, and topology spread constraints. Use when configuring GKE workload reliability, setting up PDBs, or configuring GKE health probes (liveness, readiness, startup). Don't use for disaster recovery setup or full cluster backups (use gke-backup-dr instead).
gke-workload-security
Audits, configures, and hardens workload-level security controls for Google Kubernetes Engine (GKE) applications and namespaces. Covers running cluster security audits (auditcluster.sh), configuring Workload Identity Federation (impersonation, KSA/GSA binding, and pod setup), enforcing Network Policies (default-deny…
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
cloud-architect
Designs cloud architectures, creates migration plans, generates cost optimization recommendations, and produces disaster recovery strategies across AWS, Azure, and GCP. Use when designing cloud architectures, planning migrations, or optimizing multi-cloud deployments. Invoke for Well-Architected Framework, cost…