Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add lhl/realitycheck/plugin install realityWrote 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/lhl/realitycheck/validate)<a href="https://agentmods.dev/commands/lhl/realitycheck/validate"><img src="https://agentmods.dev/badge/commands/lhl/realitycheck/validate/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/commands/lhl/realitycheck/validate"><img src="https://agentmods.dev/badge/commands/lhl/realitycheck/validate.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.00007 | $0.00577 |
| Opus 5.5 | $0.00003 | $0.00231 |
| Sonnet 5.5 | $0.00001 | $0.00115 |
| Haiku 4.5 | $0.00001 | $0.00058 |
Grade A, and why
validate 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.
What it actually says
/reality:validate - Data Integrity Check
Check database integrity and referential consistency.
Usage
/reality:validate [--strict] [--json]
CLI Invocation
Run validation using the shell wrapper:
"${CLAUDE_PLUGIN_ROOT}/scripts/run-validate.sh" [OPTIONS]
Or directly via the Python script:
uv run python scripts/validate.py [OPTIONS]
Options
--strict: Treat warnings as errors--json: Output results as JSON--mode {db,yaml}: Validation mode (default: db)--db-path PATH: Database path (for db mode)--repo-root PATH: Repository root (for yaml mode)
Checks Performed
Schema Validation
- Claim ID format:
[DOMAIN]-[YYYY]-[NNN] - Chain ID format:
CHAIN-[YYYY]-[NNN] - Valid claim types:
[F]/[T]/[H]/[P]/[A]/[C]/[S]/[X] - Valid evidence levels: E1-E6
- Credence in range [0.0, 1.0]
- Valid domains
Referential Integrity
- Claims reference existing sources
- Sources list extracted claims (backlinks)
- Chains reference existing claims
- Predictions reference existing claims
Logical Consistency
- Domain in ID matches domain field
- Chain credence ≤ MIN(claim credences)
- All
[P]claims have prediction records
Data Quality
- No empty claim text
- Embeddings present (warning if missing)
Output
OK: 0 error(s), 2 warning(s)
WARN [CLAIM_NO_EMBEDDING] TECH-2026-001: Missing embedding
WARN [CHAIN_CREDENCE_EXCEEDS_MIN] CHAIN-2026-001: Chain credence 0.8 > min claim credence 0.75
Exit Codes
0: All checks passed (warnings allowed)1: Errors found
Examples
/reality:validate
/reality:validate --strict
/reality:validate --json
/reality:validate --mode yaml --repo-root /path/to/data-repo
Related Commands
/reality:export- Export data/reality:stats- Database statistics/reality:check- Full analysis workflow
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 · 90 lines · 7 tokens per session scan A 7b19824f431a
validate is a command published in the GitHub repository lhl/realitycheck (44 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 7 tokens to every session and 577 once invoked, about $0.0000 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 commands, from other repositories
bigquery-cost-check
Audit a BigQuery SQL query or dbt model for potential cost traps before it hits production.
semantic-change-check
Audit changes to dbt Semantic Layer definitions for breaking changes and aggregation risks.
migrate
Handle the database evolution with care.
sparc-supabase-admin
🔐 Supabase Admin - You are the Supabase database, authentication, and storage specialist. You design and implement d...
cache-manage
Command "cache-manage" from amangit1314/repo-rag, covering cache-manage, usage, options, examples and view cache stats.
integrate
Start the Integration Architect lifecycle. Runs the 5-phase deterministic workflow (Discovery → UI Analysis → Contract Design → DB Alignment → Quality).