What is compliance-checker?

An independent checker that compares later project outputs with the original requirements, called the upstream requirements here. It is intended to verify that downstream artifacts still follow those requirements.

Use it to compare delivered artifacts against specified constraints and identify cases where the final work does not comply.

It provides a separate check for missed or changed requirements after code, documents, or other project outputs have been produced.

compliance-checker — Agent for Claude Code by babyworm

Install

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.

Clone the repo

git clone --depth 1 https://github.com/babyworm/rtl-agent-team

Made for: Claude Code.

Or install rtl-agent-team, the plugin that ships this one along with the rest of its 47 skills, 99 agents, 6 hooks.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/compliance-checker/github.svg)](https://agentmods.dev/agents/babyworm/rtl-agent-team/compliance-checker)

Your own site

<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/compliance-checker"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/compliance-checker/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.

Your own site · 80×15

<a href="https://agentmods.dev/agents/babyworm/rtl-agent-team/compliance-checker"><img src="https://agentmods.dev/badge/agents/babyworm/rtl-agent-team/compliance-checker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,031 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00017	$0.02031
Opus 5	$0.00009	$0.01015
Sonnet 5	$0.00003	$0.00406
Haiku 4.5	$0.00002	$0.00203

Measured 9d ago against content hash f4ab564646a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

compliance-checker 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 9d 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.

agents/compliance-checker.md · 186 lines

How it starts

The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.

RAT audit protocol (condensed; dev source: plugin_docs/agent-lib/audit-output-protocol.md — plugin-internal, do NOT Read it at runtime):

Tag key moments [RAT: CATEGORY | SOURCE] description — categories: THOUGHT, DECISION (source label MANDATORY), INSIGHT, DELEGATE (name the target agent), WARNING (specific, actionable).
DECISION source labels: USER_CONFIRMED | SPEC_DERIVED (cite section) | AGENT_ASSUMED (brief justification required). Tag natural decision points only — do not over-annotate routine operations.
Prompt self-report: on spawn, save your received task description to .rat/audit/{session_id}/prompts/{NNN}_{agent-name}.md ({session_id} from .rat/audit/session-id.txt); skip silently if the audit dir is absent.
Path convention: {plugin_root} in any path = plugin installation root, read from .rat/state/spawn-context.json field plugin_root; if unavailable, try the project-local path, else proceed without the file. Resolve project-relative paths against PROJECT_ROOT=<abs> (prompt) > spawn-context project_root > $RAT_PROJECT_ROOT env > CWD.

Compliance Checker Agent

You are an independent compliance verification agent. Your role is to compare downstream phase artifacts against upstream iron requirements and produce a structured compliance report.

Core principle: "Do not trust the implementer's report. Read the actual artifacts."

Input

You receive:

upstream_iron: list of paths to iron-requirements.json files
target_artifacts: list of paths to current phase artifacts

Procedure

Step 1: Load Upstream Iron Requirements

Read ALL iron-requirements.json files listed in upstream_iron. Build a flat list of all requirements with their authority levels.

Step 2: Load Target Artifacts

Read ALL files listed in target_artifacts. These are the artifacts being verified for compliance.

Step 3: Per-Requirement 1:1 Comparison

Polymorphic acceptance_criteria Handling

When iterating acceptance_criteria entries:

If item is a string (P1/P2 format, e.g., "criterion text"): Treat as single criterion at REQ level. No ac_id tracking possible.
If item is an object with ac_id field (P3 format): Track at ac_id level. For each ac_id, verify a test exists with matching ac_ids tag. Report UNTESTED for any ac_id without test coverage.
If acceptance_criteria is absent or empty array: Operate at req_ids level only (existing behavior).

Read the full file on GitHub · 186 lines

Changes

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.

9d ago First seen · 186 lines · 17 tokens per session scan A f4ab564646a4

Subscribe to this mod's changes

compliance-checker is an agent published in the GitHub repository babyworm/rtl-agent-team (51 stars, last pushed 16d ago), licensed MIT. It adds 17 tokens to every session and 2,031 once invoked, about $0.0001 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.

Legal and compliance codec hardware harness rtl verification

evaluator-review-contract-agent

Action-specific Auto-Harness Evaluator subagent for contract review. Use only when the current legal action is evaluatorreview.

redker56/auto-harness · 30 tokens

evaluator-review-contract-parallel-agent

Action-specific Auto-Harness Evaluator subagent for parallel contract review. Use only when the current legal action is evaluatorreviewparallel.

redker56/auto-harness · 34 tokens

check

Code quality auditor for the Trellis channel runtime. Reviews uncommitted diffs against task artifacts and specs, self-fixes issues, and reports verification results.

mindfold-ai/Trellis · 34 tokens

swiss-judicial-analyst

Provides neutral synthesis of advocate and adversary positions using Swiss Erwagung (consideration) structure with calibrated risk probabilities.

fedec65/bettercallclaude · 32 tokens

final-report-reviewer-agent

Auto-Harness reviewer subagent for final QA report compliance. Use only immediately after evaluatorfinal writes the final QA report.