deploy-dashboard

A command for deploying a finished PolicyEngine dashboard to Vercel, a service that hosts web applications, and optionally Modal for custom backend work. It also registers the dashboard in the application.

In plain words
What is it for?
Use it after merging a dashboard into the main branch to publish the frontend and, when required, its custom Modal backend.
Why use it?
It checks that the code is merged into the main branch, the working tree is clean, the build succeeds, and tests pass before deployment.

Command

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 commands/policyengine/policyengine-claude/deploy-dashboard
Clone the repo
git clone --depth 1 https://github.com/PolicyEngine/policyengine-claude
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 3,194 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. 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.00021 $0.03194
Opus 5 $0.00010 $0.01597
Sonnet 5 $0.00004 $0.00639
Haiku 4.5 $0.00002 $0.00319

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

Security

Grade B, and why

deploy-dashboard scanned grade B with 2 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 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.

Asks the agent to reveal its instructionsmediumSystem prompt leakage

Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.

**If authentication fails or shows wrong workspace:** Stop and display instructions:

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

curl -s -w "\n%{http_code}" https://policyengine--DASHBOARD_NAME-health.modal.run
commands/deploy-dashboard.md · 338 lines

How it starts

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

Deploying dashboard: $ARGUMENTS

Deploy a completed PolicyEngine dashboard to production. Run this AFTER merging your feature branch into main.

Precondition: The user should be on the main branch with a clean working tree and the dashboard code merged.

Skills Used

  • policyengine-tools — Vercel frontend deployment (all dashboards) and Modal backend deployment (only if custom-modal pattern)

Step 1: Verify Prerequisites

# Check we're on main
git branch --show-current

# Check for clean working tree
git status

# Verify build passes
bun install --frozen-lockfile && bun run build && bunx vitest run

If not on main: Tell the user to merge their feature branch first:

You're currently on branch {branch}. Please merge into main first:

git checkout main
git merge {branch}
git push

Then run /deploy-dashboard again.

If build fails: Report the error and STOP. Do not deploy broken code.

Step 2: Read the Plan

cat plan.yaml

Extract:

  • dashboard.name — for Vercel project and Modal app names
  • dashboard.zone_path — for multi-zone host rewrite verification
  • data_pattern — determines if Modal deploy is needed (custom-modal needs it; precomputed, precomputed-csv, and policyengine-api do not)
  • tech_stack.framework — should be react-nextjs (env var prefix: NEXT_PUBLIC_*)
  • embedding.register_in_apps_json — determines if apps.json update is needed
  • embedding.slug — the URL slug for policyengine.org

2a. Pre-flight: check for existing host rewrites (informational)

If this dashboard has deployed before, the host (policyengine-app-v2/website/next.config.ts) may already have rewrites pointing at it. Check so we know whether Step 5 needs to add them or they're already in place.

# Clone or pull the host repo
if [ ! -d /tmp/policyengine-app-v2 ]; then
  gh repo clone PolicyEngine/policyengine-app-v2 /tmp/policyengine-app-v2
fi
(cd /tmp/policyengine-app-v2 && git checkout main && git pull)

# Invoke the multi-zone validator in host-only mode to check all rewrite structure at once
# (beforeFiles placement, route + asset rewrite counts, destination format)

Read the full file on GitHub · 338 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 · 338 lines · 21 tokens per session scan B cf74e08a5169

Subscribe to this mod's changes

deploy-dashboard is a command published in the GitHub repository PolicyEngine/policyengine-claude (31 stars, last pushed 7d ago), licensed MIT. It adds 21 tokens to every session and 3,194 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 2 findings (asks the agent to reveal its instructions, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.