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/encode-reformgit 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.00019 | $0.05628 |
| Opus 5 | $0.00010 | $0.02814 |
| Sonnet 5 | $0.00004 | $0.01126 |
| Haiku 4.5 | $0.00002 | $0.00563 |
Grade A, and why
encode-reform 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.
- curl -sL {url} -o {PREFIX}-bill.pdf How it starts
The opening of the file, as written. The whole thing — 641 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implementing Reform: $ARGUMENTS
Coordinate a multi-agent workflow to implement a contributed policy reform (proposed bill, policy experiment, or tax change) as a complete, production-ready reform in PolicyEngine US.
GLOBAL RULE — PDF Page Numbers: Every PDF reference href MUST end with #page=XX (the file page number, NOT the printed page number). The ONLY exception is single-page PDFs. This rule applies to ALL agents in ALL phases.
GLOBAL RULE — Reform Skill: Every implementation agent (rules-engineer, test-creator, validator) MUST load /policyengine-reform-patterns in addition to their standard skills. This teaches the factory function pattern, gov/contrib/ paths, in_effect toggle, reforms: test key, and registration in reforms.py.
Arguments
$ARGUMENTS should contain:
- State and bill (required) — e.g.,
MT HB 268,CT SB-100,SC H.4216 - Or federal reform — e.g.,
CRFB AGI Surtax,Streamlined EITC - Options:
--skip-review— skip Phase 4 review-fix loop--research-only— stop after Phase 1, produce impl-spec but don't implement
Examples:
/encode-reform MT HB 268
/encode-reform CT SB-100
/encode-reform SC H.4216 --skip-review
/encode-reform CRFB AGI Surtax
/encode-reform KY HB 13 HB 152
Constants
ST = state code from $ARGUMENTS (e.g., "mt", "ct", "ky") or org name for federal (e.g., "crfb")
BILL_ID = bill identifier (e.g., "hb268", "sb100", "h4216", "agi_surtax")
PREFIX = /tmp/{ST}-{BILL_ID}
Context Window Protection
YOU (the orchestrator) ONLY read SHORT summary files (marked "Short" in the table below). All detailed data flows through disk files between agents. Never read full spec files — delegate that to agents.
Disk File Handoff Table
| File | Writer | Reader | Size |
|---|---|---|---|
{PREFIX}-type-summary.md |
bill-analyzer | Orchestrator | Short ≤15 |
{PREFIX}-bill-analysis.md |
bill-analyzer | consolidator | Full |
{PREFIX}-bill.pdf |
bill-analyzer | prep-bill-pdf | Binary |
sources/working_references.md |
bill-researcher | consolidator | Full |
{PREFIX}-impl-spec.md |
consolidator | rules-engineer, test-creator | Full |
{PREFIX}-impl-summary.md |
consolidator | Orchestrator | Short ≤20 |
{PREFIX}-checkpoint.md |
validator | Orchestrator | Short ≤15 |
{PREFIX}-test-results.md |
ci-fixer | Orchestrator | Short ≤10 |
{PREFIX}-audit-checkpoint.md |
quick-auditor | Orchestrator | Short ≤15 |
{PREFIX}-checklist.md |
review-fixer | next round fixer | Full |
{PREFIX}-final-report.md |
reporter | Orchestrator | Short ≤25 |
{PREFIX}-pr-description.md |
reporter | gh pr edit | Full |
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 · 641 lines · 19 tokens per session scan A 6d9f96e89a5c
encode-reform is a command published in the GitHub repository PolicyEngine/policyengine-claude (31 stars, last pushed 8d ago), licensed MIT. It adds 19 tokens to every session and 5,628 once invoked, about $0.0001 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 commands, from other repositories
review-epo-claims
Analyze patent claims for EPO Art. 84 EPC compliance - clarity, conciseness, support by description.
review-policy
Review a policy document for structure, coverage, and language quality.
at-dsgvo
You are helping an enterprise architect generate an Austrian Data Protection Assessment — the Austrian-specific GDPR layer applied by the Datenschutzbehörde (DSB) under the Datenschutzgesetz (DSG 2018, BGBl. I Nr. 165/1999 as amended). Run this after /arckit:eu-rgpd to add Austrian obligations that go beyond the EU…
au-soci-cirmp
You are an enterprise architect generating a Security of Critical Infrastructure Act 2018 (SOCI Act) / Critical Infrastructure Risk Management Program (CIRMP) governance and evidence pack for an Australian critical infrastructure asset or potentially regulated entity.
au-aescsf
You are an enterprise architect generating an Australian Energy Sector Cyber Security Framework (AESCSF) maturity assessment for an Australian energy-sector project, asset, market interface, OT environment, DER platform, or regulated energy business capability.
au-pspf
You are an enterprise architect generating a Protective Security Policy Framework (PSPF) compliance assessment for an Australian Government entity or contractor handling government information.