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/audit-state-taxgit 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/audit-state-tax)<a href="https://agentmods.dev/commands/policyengine/policyengine-claude/audit-state-tax"><img src="https://agentmods.dev/badge/commands/policyengine/policyengine-claude/audit-state-tax.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.00021 | $0.03649 |
| Opus 5 | $0.00010 | $0.01825 |
| Sonnet 5 | $0.00004 | $0.00730 |
| Haiku 4.5 | $0.00002 | $0.00365 |
Grade A, and why
audit-state-tax 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 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Download it: `curl -L -o /tmp/{state}-audit-source.pdf "URL"` How it starts
The opening of the file, as written. The whole thing — 395 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auditing State Tax PR: $ARGUMENTS
READ-ONLY MODE: This command audits parameter values in a state income tax PR against official PDF sources and posts findings to GitHub. It does NOT make code changes.
Arguments
$ARGUMENTS should contain:
- PR number (required) — e.g.,
7130 - PDF URL (optional) — link to the state's official tax form instructions or tax guide. If omitted, the command will auto-discover the source.
- Options:
--local— show findings locally only, skip GitHub posting--full— audit ALL implemented parameters (not just PR changes) against the PDF
Examples:
/audit-state-tax 7130
/audit-state-tax 7130 --full
/audit-state-tax 7130 --local
/audit-state-tax 7130 https://oregon.gov/.../form-or-40-inst_2025.pdf
/audit-state-tax 7130 https://oregon.gov/.../form-or-40-inst_2025.pdf --full
Phase 0: Parse Arguments & Setup
Parse $ARGUMENTS:
- PR_NUMBER: first numeric argument
- PDF_URL: first URL argument (may be empty — will auto-discover in Phase 1.5)
- LOCAL_ONLY: true if --local flag present
- FULL_AUDIT: true if --full flag present
Determine Posting Mode
If --local flag: Skip prompt, proceed in local-only mode.
If no flag: Use AskUserQuestion:
Question: "Post audit findings to GitHub when complete?"
Options:
- "Yes, post to GitHub" (default)
- "No, show locally only"
Phase 1: Gather PR Context
Collect information about the PR without switching branches:
gh pr view $PR_NUMBER --json title,body,author,baseRefName,headRefName
gh pr diff $PR_NUMBER > /tmp/state-tax-pr-diff.txt
From the diff, identify:
- State abbreviation (e.g.,
or,md) from file paths likeparameters/gov/states/{st}/tax/ - Tax year being updated
- Files changed: parameter YAMLs, variable Python files, tests
- What topics are covered: rates, deductions, credits, exemptions, etc.
Phase 1.5: Auto-Discover PDF Source (if no URL provided)
Skip this phase if the user provided a PDF URL.
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 · 395 lines · 21 tokens per session scan A d012e2063aed
audit-state-tax is a command published in the GitHub repository PolicyEngine/policyengine-claude (32 stars, last pushed 3d ago), licensed MIT. It adds 21 tokens to every session and 3,649 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
valuation-methods
Valuation methods analysis — multiples, DCF inputs, PEG integration, valuation assumption extraction.
merit-reconcile
Preview or check the status of Stripe → Merit payout reconciliation (read-only).
audit-checklist
Perform an internal audit, review controls, or prepare for an external financial audit.
scan
Scan AWS account for cost optimization.
finops-status
Orientation — say where an opportunity or assignment sits in the five-step FinOps lifecycle and what unlocks next. Useful when a record has no active stage: an opportunity while its assignments do the work, an assignment whose plan has not been approved yet, or a rejected or archived assignment. Read-only; mutates…
archive-ledger
../../../shared/commands/archive-ledger.md.