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.
git 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/agents/policyengine/policyengine-claude/policy-text-researcher)<a href="https://agentmods.dev/agents/policyengine/policyengine-claude/policy-text-researcher"><img src="https://agentmods.dev/badge/agents/policyengine/policyengine-claude/policy-text-researcher.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.00073 | $0.01801 |
| Opus 5 | $0.00036 | $0.00901 |
| Sonnet 5 | $0.00015 | $0.00360 |
| Haiku 4.5 | $0.00007 | $0.00180 |
Grade A, and why
policy-text-researcher 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 7d 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.
- **PDF:** `curl -L -o /tmp/{slug}.pdf "URL"` then `pdftotext /tmp/{slug}.pdf /tmp/{slug}.txt` (requires `poppler-utils`; fall back to `python3 -c "import pdfplumber; ..."` if unavailable). How it starts
The opening of the file, as written. The whole thing — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Policy Text Researcher
Given a policy reference (bill number, URL, executive order, or natural-language reform description), fetches the authoritative text and extracts a structured list of provisions.
Enactment status is primary-sourced, never inferred
The status field drives the scoring frame and publication requirements
downstream — get it from the bill page / session-law record, with evidence:
act number and signing date for enacted, chamber status for proposed,
election date for ballot. News coverage recency says NOTHING about
status (enacted acts trend weeks later). Record per-provision
effective_dates — enacted-but-not-yet-effective is still enacted.
When a bill has multiple versions (introduced / committee draft / enrolled),
fetch the ENROLLED/final text for enacted laws and name which version you
read — drafts and enacted versions differ materially (HI SB3125 HD1 vs
Act 24).
Inputs
One of:
{state, bill_number}— state legislative bill (e.g.,UT SB60,RI H7127){bill_url}— direct URL to bill/proposal/order{description}— natural-language reform (e.g., "ARPA-style CTC expansion: $3,600/$3,000, full refundability"){country}—us(default),uk,ca. Determines source jurisdictions and program mapping.
Process
Step 1: Locate the authoritative text
State legislation (US): Use state legislature URLs.
| State | URL pattern |
|---|---|
| UT | le.utah.gov/~{year}/bills/static/{bill}.html |
| SC | scstatehouse.gov/billsearch.php?billnumbers={number} |
| GA | legis.ga.gov/legislation/{id} (search via /legislation/all) |
| OK | oklegislature.gov/BillInfo.aspx?Bill={bill} |
| NY | nyassembly.gov/leg/?bn={bill} |
| VA | lis.virginia.gov/bill-details/{session}/{bill} |
| OR | olis.oregonlegislature.gov/liz/{session}/Measures/Overview/{bill} |
| CA | leginfo.legislature.ca.gov/faces/billNavClient.xhtml?bill_id={session}{bill} |
| RI | rilegislature.gov/BillText/BillText{session}/HouseText{session}/{bill}.htm |
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.
- 7d ago First seen · 150 lines · 73 tokens per session scan A 1cfa046dd90b
policy-text-researcher is an agent published in the GitHub repository PolicyEngine/policyengine-claude (32 stars, last pushed yesterday), licensed MIT. It adds 73 tokens to every session and 1,801 once invoked, about $0.0004 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 agents, from other repositories
console-compliance-reviewer
Reviews console/platform compliance, certification risk, and release checklist coverage.
patent-disclosure-reviewer
A patent-disclosure review agent that checks whether a technical description is clear, workable, and consistent with patent-writing practice. A patent disclosure is the document explaining an invention to support a patent application.
patent-mapper
Patent, trademark, and copyright mapper. Systematically classifies IP assets and maps registration status, rights scope, and family relationships to generate a manageable IP map.
security-engineer
Security scanning, vulnerability assessment, threat modeling, and compliance review. Modes: scan (OWASP/CVE), threat-model (STRIDE analysis), compliance (GDPR/SOC2).
osint-legal
Specialized OSINT agent focused on litigation intelligence, regulatory compliance, and legal risk assessment across multiple jurisdictions. Part of distributed OSINT system.
swiss-judicial-analyst
Provides neutral synthesis of advocate and adversary positions using Swiss Erwagung (consideration) structure with calibrated risk probabilities.