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 agents/policyengine/policyengine-claude/reform-classifiergit 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.00064 | $0.01479 |
| Opus 5 | $0.00032 | $0.00740 |
| Sonnet 5 | $0.00013 | $0.00296 |
| Haiku 4.5 | $0.00006 | $0.00148 |
Grade A, and why
reform-classifier 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reform Classifier
The Stage-2 gate of /analyze-policy. Takes the provisions + parameter-locator verdicts and returns one of three outcomes:
parametric— every provision maps to an existing PolicyEngine parameter. The microsim runner can execute the reform-dict as-is.structural— at least one provision requires new variable logic, formula changes, or a new sub-program. The reform needs model changes before it can be scored; emit a backlog note.not-possible— the reform falls outside PolicyEngine's modeling scope (e.g., a non-tax-benefit policy, a change to the tax administration process, a behavioral mandate).
Inputs
provisions(frompolicy-text-researcher)parameter_locator_verdicts(one per provision, fromparameter-locator)jurisdiction
Decision tree
For each provision:
- Did
parameter-locatorreturnverdict: "parametric"withconfidence: "high"? → parametric. - Did it return
verdict: "deployed-model-lag"? → deployed-model-lag for this provision (the parameter exists on master but not on the deployed API release; nothing structural to fix here — just wait for the next release). - Did it return
verdict: "no-parameter"with astructural_hint? → structural for this provision. - Does the provision describe something not in scope? → not-possible for this provision.
- Out of scope includes: tax administration, audit policies, IRS staffing, enforcement, behavioral mandates without dollar consequences, non-tax-benefit programs (housing zoning, education curriculum), retroactive provisions that PolicyEngine cannot back-date.
Aggregate across provisions (order matters — first match wins):
- If any deployed-model-lag and no structural/not-possible → reform is
deployed-model-lag(overall). Emitmissing_pathsandnext_action: "Wait for next PE-{country} release, or re-run with --skip-microsim for process-test mode."Stop the pipeline. - If any not-possible → reform is
not-possible(overall). Emit rationale; stop. - If any structural → reform is
structural(overall). Emit which provisions need model changes withmodel_change_estimate; stop the pipeline. - If all parametric → reform is
parametric. Proceed to Stage 3/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 · 118 lines · 64 tokens per session scan A fd9c95faa00b
reform-classifier is an agent published in the GitHub repository PolicyEngine/policyengine-claude (31 stars, last pushed 7d ago), licensed MIT. It adds 64 tokens to every session and 1,479 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.