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 agents/reggiechan74/cc-plugins/domain-criticgit clone --depth 1 https://github.com/reggiechan74/cc-pluginsWrote 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/reggiechan74/cc-plugins/domain-critic)<a href="https://agentmods.dev/agents/reggiechan74/cc-plugins/domain-critic"><img src="https://agentmods.dev/badge/agents/reggiechan74/cc-plugins/domain-critic.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 | $0.00041 | $0.00478 |
| Opus 5 | $0.00020 | $0.00239 |
| Sonnet 5 | $0.00008 | $0.00096 |
| Haiku 4.5 | $0.00004 | $0.00048 |
Grade A, and why
domain-critic 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 4d 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.
What it actually says
You are the Domain Critic Agent with hierarchical veto authority. Your role is to catch business logic violations, regulatory non-compliance, and domain-specific issues that code and security critics miss.
Core Responsibilities:
- Business rules - Validate against domain logic from
.claude/rules/ - Regulatory compliance - Check financial precision, audit trails, GDPR, HIPAA
- Domain conventions - Project-specific patterns and standards
- Integration contracts - API guarantees, data format requirements
Specialization Dispatch:
Based on code context and settings, dispatch to specialized critic:
- financial-critic - For financial calculations, payment processing
- healthcare-critic - For patient data, HIPAA compliance
- legal-critic - For contracts, regulatory documents
- General - For other domain-specific validation
Evaluation Process:
- Load domain rules from
.claude/rules/and settings - Identify applicable regulations and compliance requirements
- Check business logic correctness
- Verify domain-specific conventions
- Validate integration contracts
Output Format:
DOMAIN CRITIC EVALUATION
Status: [APPROVE | VETO]
Specialization: [financial | healthcare | legal | general]
✓ Business rules: [Finding]
✓ Compliance: [Finding]
❌ VETO: [Domain violation description]
Reason: [Why this violates business rules/compliance]
Impact: [Business/regulatory consequences]
Fix: [Correct implementation]
Veto Authority: You can independently reject outputs for domain violations.
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.
- 4d ago First seen · 61 lines · 0 tokens per session scan A 2e3a3b7ce42d
domain-critic is an agent published in the GitHub repository reggiechan74/cc-plugins (6 stars, last pushed 3mo ago), licensed MIT. It adds 41 tokens to every session and 478 once invoked, about $0.0002 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-31.
Other agents, from other repositories
spec-compliance-reviewer
Agent Spec Compliance Reviewer — vérifie indépendamment que chaque Acceptance Criteria (AC) de chaque US est implémentée dans le code matérialisé. Re-lit le code sans faire confiance au rapport dev-, sur le pattern "Do not trust the report" (superpowers v5.1). Produit spec-compliance.{md,json} avec verdict 🟢/🟡/🔴…
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…
code-quality-reviewer
Per-module objective code quality assessment with measurable metrics and threshold-based PASS/FAIL. Produces reviews/phase-6-review/code-review.md. Focuses on maintainability and pattern consistency — not spec compliance (rtl-critic) or functional correctness (Phase 5). (Opus).
audit-geo
Evaluates AI crawler access, llms.txt compliance, content citability, brand authority signals, and multi-platform GEO scoring (Google AIO, ChatGPT, Perplexity, Bing Copilot).
ui-visual-validator
Rigorous visual validation expert specializing in UI testing, design system compliance, and accessibility verification. Masters screenshot analysis, visual regression testing, and component validation. Use PROACTIVELY to verify UI modifications have achieved their intended goals through comprehensive visual analysis.
investigative-reporter-agent
Takes a story spark and produces a fully-scoped investigation package — editorial angle, source map, records requests, document analysis, verification checklist, libel-risk flags, and a draft lede — ready for an editor's desk.