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/create-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.00040 | $0.05493 |
| Opus 5 | $0.00020 | $0.02746 |
| Sonnet 5 | $0.00008 | $0.01099 |
| Haiku 4.5 | $0.00004 | $0.00549 |
Grade A, and why
create-dashboard 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 640 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Creating Dashboard: $ARGUMENTS
Coordinate a multi-agent workflow to plan, scaffold, implement, validate, and commit a production-ready PolicyEngine dashboard application.
When to use vs /new-tool
/create-dashboard— multi-page policy analysis apps with plan/scaffold/implement/validate phases. Think "child poverty rates by state under different CTC reform scenarios" — multiple views, filters, embedded charts, backend calls./new-tool— bootstrapper for a single-purpose interactive calculator (e.g., "SALTernative", "ACA-calc"). Blank canvas + design tokens; you implement the specific tool logic yourself.
Arguments
$ARGUMENTS should contain:
- Dashboard description (required) — a natural-language description of the desired dashboard
- Options:
--repo NAME_OR_PATH— use an existing repo (searches sibling of cwd,~/Documents/PolicyEngine/,~/PolicyEngine/,~/)--skip-init— use current working directory as the repo (no repo creation or cloning)--skip-validate— skip the Phase 5 validation loop--auto-confirm— headless mode: no AskUserQuestion gates (see "Headless mode" below)--reform-json PATH— path to a validated reform_dict JSON file; the planner must treat it as the canonical reform definition (typically produced by a prior /analyze-policy run)--dry-run— with--auto-confirm: run Phase 0 argument parsing + Phase 1 planning only; no repo creation, no build, no push--horizon {1|10}— impact time horizon (default1).10adds 10-year series via the API's budget-window compute (~15-25 min extra) — opt in only when the dashboard needs it--no-household— omit the household example page (included by default)
Standard pages: every policy-analysis dashboard includes a policy
explanation page (provisions + source links + parameter table) and a
validation page (results vs external benchmarks, versions, methodology) in
addition to the impacts pages — see dashboard-planner.md "Step 1b". The
household page is standard unless --no-household; its inputs must mirror
the reform's levers (CTC → children/ages; SS taxation → benefit + filing
status + other income) with 3-5 representative precomputed preset cases —
see dashboard-planner.md Step 1b item 4.
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 · 640 lines · 40 tokens per session scan A 6a3728df8baf
create-dashboard is a command published in the GitHub repository PolicyEngine/policyengine-claude (31 stars, last pushed 7d ago), licensed MIT. It adds 40 tokens to every session and 5,493 once invoked, about $0.0002 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-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.
constitution
Create or update the project constitution from interactive or provided principle inputs.
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.