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/reform-pipelinegit 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/commands/policyengine/policyengine-claude/reform-pipeline)<a href="https://agentmods.dev/commands/policyengine/policyengine-claude/reform-pipeline"><img src="https://agentmods.dev/badge/commands/policyengine/policyengine-claude/reform-pipeline.svg" alt="Measured on agentmods" 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.00050 | $0.02410 |
| Opus 5 | $0.00025 | $0.01205 |
| Sonnet 5 | $0.00010 | $0.00482 |
| Haiku 4.5 | $0.00005 | $0.00241 |
Grade A, and why
reform-pipeline 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 5d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reform Pipeline: $ARGUMENTS
The single-command version of the CRM research pipeline: discover → score → verify → publish, with confirmation gates inline instead of the Command Center. Use this when you want to drive the whole chain yourself for a topic ("healthcare", "child tax credit", "Utah income tax") rather than waiting for the newsroom's scheduled discovery.
Arguments
$ARGUMENTS should contain:
- Topic or reform (required) — a policy area to scan for ("healthcare", "social security taxation"), OR a concrete reform/bill id ("UT SB60") to skip discovery and go straight to scoring.
- Options:
--country {us|uk|ca}(defaultus)--horizon {1|10}(default1; 10-year adds 15-25 min of API compute)--publish {auto|tracker|dashboard|none}(defaultauto— route by the standard rules;nonestops after the verified analysis)--auto-confirm— skip the confirmation gates (headless / CI use)--dry-run— publication workflows run withdry_run=true(compute + validate, no Supabase writes / PRs / pushes)
Examples:
/reform-pipeline healthcare
/reform-pipeline "social security taxation" --publish dashboard --horizon 10
/reform-pipeline "UT SB60" --publish tracker --dry-run
Phase 0 — Clarify (skipped with --auto-confirm or when fully specified)
Before scanning anything, resolve what's underspecified with ONE AskUserQuestion round (ask only the questions the arguments left open — a concrete bill id leaves nothing to ask):
- Sources (multi-select): where should discovery look?
- CRM newsroom (needs
CRM_API_URL+CRM_API_TOKEN; only offer when reachable) - Web news search (last 14 days)
- Bill trackers (congress.gov federal search; state bills named in coverage)
- Default: all available.
- CRM newsroom (needs
- Scope (when the topic doesn't imply it): federal, a specific state, or either — this changes both where to look and the eventual publication route (state → tracker, federal → dashboard).
- Publication intent (when
--publishwasn't passed): auto-route / bill tracker / dashboard / analysis only. Sets the--publishvalue. - Recency window only if the user's phrasing suggests older material ("that bill from March") — default 14 days otherwise, don't ask.
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.
- 5d ago First seen · 196 lines · 50 tokens per session scan A 9891a80a538c
reform-pipeline is a command published in the GitHub repository PolicyEngine/policyengine-claude (32 stars, last pushed 3d ago), licensed MIT. It adds 50 tokens to every session and 2,410 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 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.
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.