frontend

A specialist agent for frontend applications and Vercel deployments, where Vercel is a service that builds and hosts web projects. It works inside a specified codebase and follows a layered troubleshooting process.

In plain words
What is it for?
Use it to diagnose Vercel build errors, deployment and preview problems, environment-variable issues, frontend infrastructure issues, and related application fixes.
Why use it?
It helps narrow deployment failures to the build system, web framework, application code, or DNS instead of investigating everything at once.

Agent

Install

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.

agentmods
npx agentmods add agents/varienos/agentic-workflow/frontend.skeleton
Clone the repo
git clone --depth 1 https://github.com/varienos/agentic-workflow
Per session 1 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,612 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00001 $0.01612
Opus 5 $0.00000 $0.00806
Sonnet 5 $0.00000 $0.00322
Haiku 4.5 $0.00000 $0.00161

Measured 2d ago against content hash e49f998a25f6, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

frontend scanned grade C 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 2d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

rm -rf node_modules && npm ci
Agentbase/templates/modules/deploy/vercel/agents/frontend.skeleton.md · 168 lines

How it starts

The opening of the file, as written. The whole thing — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Frontend & Vercel Deploy Uzmani

Vercel deploy surecleri, build sorunlari, ortam degiskenleri ve frontend altyapisi icin uzman agent. Cagrilma: Ana agent tarafindan Vercel deploy veya frontend altyapisi sorunlarinda teammate olarak spawn edilir.

Calisma Siniri

Bu agent Agentbase den spawn olur ve ../Codebase/ uzerinde calisir.

  • Proje dosyalarini (src/, app/, vb.) okuyabilir ve degistirebilir
  • Codebase icinde .claude/ dizini OLUSTURAMAZ
  • Codebase icinde CLAUDE.md, .mcp.json, .claude-ignore YAZAMAZ
  • Tum agent config dosyalari Agentbase/.claude/ altinda yasar

Temel Yaklasim

Sorun Giderme Metodolojisi

  1. Belirtileri topla — Build hatalari, deployment loglari, preview URL durumu
  2. Katmani belirle — Sorun hangi katmanda? (Vercel Build → Framework → Uygulama → DNS)
  3. Hipotez olustur — En olasi nedenler listesi (en yaygindan basla)
  4. Dogrula — Her hipotezi sirayla test et
  5. Coz — Dogrulanan sorunu duzelt
  6. Dokumante et — Ne yapildigini ve neden yapildigini kaydet

Katmanli Debug Sirasi

1. Vercel Dashboard    → Build loglari, deployment durumu, fonksiyon loglari
2. Framework Build     → Next.js/React build ciktisi, TypeScript hatalari
3. Ortam Degiskenleri  → Eksik veya yanlis yapilandirilmis env degiskenleri
4. Vercel Config       → vercel.json, redirects, rewrites, headers
5. DNS / Domain        → Custom domain yapilandirmasi, SSL durumu

Guvenlik Kurallari

  • Secret'lari ASLA kod icine yazma — Vercel Environment Variables kullan
  • Preview deployment'larda production secret'larini KULLANMA — ayri env seti olustur
  • NEXT_PUBLIC_ ile baslayan degiskenlerin client-side'da gorunur oldugunu unutma
  • Vercel API Token'ini ASLA acik metin olarak paylas

Read the full file on GitHub · 168 lines

Changes

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.

  1. 2d ago First seen · 168 lines · 1 tokens per session scan C e49f998a25f6

Subscribe to this mod's changes

frontend is an agent published in the GitHub repository varienos/agentic-workflow (58 stars, last pushed 2mo ago), licensed MIT. It adds 1 tokens to every session and 1,612 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other agents, from other repositories

product-manager

Turns a high-level ask into a crisp, exec-ready PRD with acceptance criteria and scope.

shanraisshan/claude-code-best-practice · 22 tokens

milestone-designer

The kept-warm seat for one milestone — owns milestones/ /spec.md's chunk decomposition (per chunk WHAT to build + WHAT to test, never HOW), stays alive through the milestone's whole lifecycle (resume-dont-respawn, spawned fresh only at milestone start), and answers implementer/reviewer consultations through the…

Fredasterehub/kiln · 326 tokens

al-presales

Technical PreSales Agent for AL/Business Central projects. Specializes in project planning, cost estimation (time and budget), feasibility analysis, SWOT/risk assessment, and technical documentation. Use when estimating projects, sizing proposals, or performing feasibility analysis.

javiarmesto/ALDC-AL-Development-Collection · 53 tokens

handoff-recorder

The stop-writing seat for the handoff pair (handoff.md plus state.json's own stop fields) — a purpose-named seat backed by one handoff.js write-stop machine command, holding Bash for that command alone; Kiln supplies the operator's exact question or rationale as structured data and does not write or paraphrase it.…

Fredasterehub/kiln · 262 tokens

engineering-manager

The Engineering Manager of the aSPARK team. Use in the Plan phase (/sprint-plan) to turn an approved spec into a technical plan: architecture decision with rejected alternatives, ordered task breakdown, test strategy and risks. Also use when a plan must be revised after review or QA findings.

a-lottes/aSPARK · 62 tokens

project-manager

Project delivery specialist. Invoke for sprint planning, delivery milestones, dependency mapping, RAID logs, status reports, retrospectives, and cross-functional execution coordination. Distinct from product-manager, use this for delivery and execution, not product discovery.

pranav8494/team-of-agents · 50 tokens