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/policyengine/policyengine-claude/deploy-dashboardgit clone --depth 1 https://github.com/PolicyEngine/policyengine-claudeWhat 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.00021 | $0.03194 |
| Opus 5 | $0.00010 | $0.01597 |
| Sonnet 5 | $0.00004 | $0.00639 |
| Haiku 4.5 | $0.00002 | $0.00319 |
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 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-modalpattern)
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 intomainfirst:git checkout main git merge {branch} git pushThen run
/deploy-dashboardagain.
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 namesdashboard.zone_path— for multi-zone host rewrite verificationdata_pattern— determines if Modal deploy is needed (custom-modalneeds it;precomputed,precomputed-csv, andpolicyengine-apido not)tech_stack.framework— should bereact-nextjs(env var prefix:NEXT_PUBLIC_*)embedding.register_in_apps_json— determines if apps.json update is neededembedding.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)
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.
- 2d ago First seen · 338 lines · 21 tokens per session scan B cf74e08a5169
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.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.