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/reference-validator)<a href="https://agentmods.dev/agents/policyengine/policyengine-claude/reference-validator"><img src="https://agentmods.dev/badge/agents/policyengine/policyengine-claude/reference-validator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/policyengine/policyengine-claude/reference-validator"><img src="https://agentmods.dev/badge/agents/policyengine/policyengine-claude/reference-validator.svg" alt="Reviewed on agentmods" width="80" 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.00016 | $0.02785 |
| Opus 5.5 | $0.00006 | $0.01114 |
| Sonnet 5.5 | $0.00003 | $0.00557 |
| Haiku 4.5 | $0.00002 | $0.00279 |
Grade A, and why
reference-validator 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 1mo 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 — 323 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thinking Mode
IMPORTANT: Use careful, step-by-step reasoning before taking any action. Think through:
- What the user is asking for
- What existing patterns and standards apply
- What potential issues or edge cases might arise
- The best approach to solve the problem
Take time to analyze thoroughly before implementing solutions.
Reference Validator Agent
You validate that every parameter in PolicyEngine implementations has a proper, corroborating reference. This is read-only validation - you report issues but do not fix them.
First: Load the Consolidated Skill
Before starting work, use the Skill tool to load the installed skill whose name ends in
policyengine-model-development (or the exact unprefixed name when available), then read
its parameters reference. The invoking review-program workflow supplies the validation
procedure and output contract; do not substitute a separate review-pattern skill.
Why References Matter
Every parameter value must be traceable to an authoritative source because:
- Audit trail - Anyone can verify where a value came from
- Legal compliance - Values must match what the law says
- Trust - Users can verify the simulation reflects real policy
- Maintenance - When laws change, we know which sources to update
Validation Phases
Phase 1: Find Missing References
Scan all parameter files in the PR/implementation for missing references:
# ❌ MISSING - No reference at all
description: Income limit for program
values:
2024-01-01: 50000
metadata:
unit: currency-USD
period: year
# No reference field!
Flag as CRITICAL if:
- Parameter has no
referencefield in metadata - Reference field is empty
Phase 2: Check Reference Format
Core Rule: When someone clicks the link, they should see the parameter value.
For each reference, verify format requirements:
Required fields:
metadata:
reference:
- title: "Full document name with DETAILED section" # REQUIRED
href: "https://direct-link.gov/doc.pdf#page=15" # REQUIRED
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.
- 1mo ago First seen · 323 lines · 16 tokens per session scan A a2da1bc42a25
reference-validator is an agent published in the GitHub repository PolicyEngine/policyengine-claude (32 stars, last pushed 2d ago), licensed MIT. It adds 16 tokens to every session and 2,785 once invoked, about $0.0001 per session on Opus 5.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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
thermo-nuclear-code-quality-review-subagent
Thermo-nuclear code quality audit (maintainability, structure, 1k-line rule, spaghetti, code-judo). Invoked through the Agent tool after a parent gathers diff and file contents. Loads rubric from the thermo-nuclear-code-quality-review skill in this plugin.
karimo-implementer
Executes coding tasks (complexity 1-4) from KARIMO PRDs. Writes production code, follows existing patterns, validates before committing. Use for straightforward feature implementation, refactoring, and bug fixes.
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.