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/policyengine/policyengine-claude/policyengine-toolsnpx skills add PolicyEngine/policyengine-claude --skill policyengine-toolsgit 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.00179 | $0.03839 |
| Opus 5 | $0.00089 | $0.01920 |
| Sonnet 5 | $0.00036 | $0.00768 |
| Haiku 4.5 | $0.00018 | $0.00384 |
Grade A, and why
policyengine-tools 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Vercel. Modal apps can silently disappear — if the frontend gets network errors, `curl` the How it starts
The opening of the file, as written. The whole thing — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PolicyEngine standalone tools
How to build calculators, dashboards, and visualizations that deploy independently to Vercel
and slot into policyengine.org as Next.js multizones. New tools are their own repos; the
host (policyengine-app-v2/website/) proxies a URL path to each tool's Vercel deployment.
Required stack
- Next.js (App Router) — not Pages Router, not Vite as the app bundler (Vite only backs
Vitest).
next.config.ts+app/withlayout.tsx+page.tsx, TypeScript. - Tailwind v4, CSS-first — no
tailwind.config.{ts,js}.globals.cssis exactly:@import "tailwindcss"; @import "@policyengine/ui-kit/theme.css"; /* both required; Tailwind must come first */ - PostCSS is required for Next — create
postcss.config.mjswith{ plugins: { "@tailwindcss/postcss": {} } }and install@tailwindcss/postcss+postcssas devDeps. (A Vite tool uses the@tailwindcss/viteplugin instead and needs no PostCSS config.) The theme.css header itself states@tailwindcss/postcssis mandatory — the older "no postcss.config" guidance was wrong. @policyengine/ui-kit(bun add @policyengine/ui-kit) — use its components before building your own. See policyengine-design for the full 0.4.0 export list.- bun for everything (
bun install,bun run build,bunx;bun.lockcommitted). - Vercel deploy under the
policy-enginescope. Static-only tools may useoutput: 'export'; tools with a Modal backend stay server-rendered.
Scaffold: bunx create-next-app@latest my-tool --ts --app --tailwind --eslint --import-alias "@/*",
then bun add @policyengine/ui-kit and set up globals.css as above.
ui-kit components (verified 0.4.0)
Prefer these over hand-rolled equivalents; import from @policyengine/ui-kit:
| Need | Component |
|---|---|
| Page shell / layout | DashboardShell, SidebarLayout, SingleColumnLayout, InputPanel, ResultsPanel, Stack, Group, Container |
| Header + footer | Header, Footer (Header props: navItems, logoSrc, linkComponent, countries — not variant/navLinks) |
| Inputs | CurrencyInput, NumberInput, SelectInput, CheckboxInput, SliderInput, InputGroup |
| Primitives | Button, Card, Badge, Tabs, Dialog, Select, Tooltip, Alert, Switch, SegmentedControl, … |
| Display | MetricCard, SummaryText, DataTable, PolicyEngineWatermark |
| Charts | ChartContainer, PEBarChart, PELineChart, PEAreaChart, PEWaterfallChart |
| Maps | USDistrictChoroplethMap, UKConstituencyChoroplethMap, HexagonalMap, HouseholdGraph |
| Utils | formatCurrency, formatPercent, formatNumber, cn, logos |
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 · 266 lines · 179 tokens per session scan A 069a757b4937
policyengine-tools is a skill published in the GitHub repository PolicyEngine/policyengine-claude (31 stars, last pushed 7d ago), licensed MIT. It adds 179 tokens to every session and 3,839 once invoked, about $0.0009 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.