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 skills add PolicyEngine/policyengine-claude --skill policyengine-appgit clone --depth 1 https://github.com/PolicyEngine/policyengine-claudeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/policyengine/policyengine-claude/policyengine-app)<a href="https://agentmods.dev/skills/policyengine/policyengine-claude/policyengine-app"><img src="https://agentmods.dev/badge/skills/policyengine/policyengine-claude/policyengine-app/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/policyengine/policyengine-claude/policyengine-app"><img src="https://agentmods.dev/badge/skills/policyengine/policyengine-claude/policyengine-app.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00174 | $0.01993 |
| Opus 5.5 | $0.00070 | $0.00797 |
| Sonnet 5.5 | $0.00035 | $0.00399 |
| Haiku 4.5 | $0.00017 | $0.00199 |
Grade C, and why
policyengine-app scanned grade C 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 1mo 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.
- When `bun install` fails, try at most 2 fixes, then ask. Never `rm -rf node_modules`, Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **`curl` is NOT verification.** An SPA (and a streamed Next page) returns a 200 HTML shell How it starts
The opening of the file, as written. The whole thing — 140 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PolicyEngine app v2
PolicyEngine/policyengine-app-v2 is the frontend served at policyengine.org. It is
mid-migration: a Next.js 15 App Router host lives in website/ and is the live apex,
while a legacy Vite SPA in app/ still owns the calculator surface and is being ported
page by page. Verify the current stack from package.json files before trusting any summary
— this repo moves fast.
Monorepo layout
Bun workspaces + Turbo (packageManager: [email protected], root turbo.json). Workspaces:
packages/*, app, website, calculator-app.
| Path | What | Bundler |
|---|---|---|
website/ |
@policyengine/website — Next.js 15 App Router host (live apex, marketing/research/tools) |
Next 15 + Turbopack |
app/ |
policyengine-app-v2 — legacy Vite SPA (calculator: policies, households, reports, simulations) |
Vite 6 |
calculator-app/ |
standalone calculator workspace | Vite |
packages/ |
shared workspace packages | — |
Root scripts run through Turbo: bun run build → turbo run build; bun run dev runs the
Next host (scripts/dev-server-next.mjs); bun run dev:legacy runs the Vite app.
Tech stack (verified from package.json)
There is no third-party component framework — UI is built from radix-ui primitives plus local components. Do not add one.
website/:next^15.3.3,radix-ui^1.4.3,@tabler/icons-react,tailwindcssv4 (@tailwindcss/postcss),class-variance-authority,react19,react-plotly.js(maps),framer-motion,fuse.js,react-markdown.app/:vite6,react-router-dom7,@tanstack/react-query,@reduxjs/toolkit+react-redux,recharts^3.7.0,@tabler/icons-react,tailwindcssv4 (@tailwindcss/vite), Storybook.- Both pin
@policyengine/ui-kit^0.4.0. See the policyengine-design skill for its API.
useDisclosure / useMediaQuery / useViewportSize in app/src/hooks/ are local
reimplementations — not a dependency.
App Router page pattern (website/)
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.
- 1mo ago First seen · 140 lines · 174 tokens per session scan C efcd2fc6d374
policyengine-app is a skill published in the GitHub repository PolicyEngine/policyengine-claude (32 stars, last pushed 2d ago), licensed MIT. It adds 174 tokens to every session and 1,993 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.