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/check)<a href="https://agentmods.dev/commands/lhl/realitycheck/check"><img src="https://agentmods.dev/badge/commands/lhl/realitycheck/check/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/check"><img src="https://agentmods.dev/badge/commands/lhl/realitycheck/check.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.01136 |
| Opus 5.5 | $0.00006 | $0.00454 |
| Sonnet 5.5 | $0.00003 | $0.00227 |
| Haiku 4.5 | $0.00002 | $0.00114 |
Grade A, and why
check 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 — 121 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/reality:check - Full Analysis Workflow
The flagship Reality Check command for rigorous source analysis.
Core Methodology: See methodology/workflows/check-core.md for the complete 3-stage analysis methodology, evidence hierarchy, claim types, and extraction format.
Before starting, read methodology/workflows/check-core.md and follow its Output Contract. In particular: the analysis markdown must include claim tables with evidence levels and credence (do not omit).
IMPORTANT: Always write to the DATA repository (pointed to by REALITYCHECK_DATA), never to the framework repository. If you see scripts/, tests/, integrations/ - you're in the wrong repo.
Usage
/reality:check <url>
/reality:check <url> --domain TECH --quick
/reality:check <source-id> --continue
/reality:check --continue
Arguments
url: URL of the source to analyze--domain: Primary domain hint (TECH/LABOR/ECON/GOV/SOC/RESOURCE/TRANS/GEO/INST/RISK/META)--quick: Skip Stage 3 (dialectical analysis) for faster processing--no-register: Analyze without registering to database--continue: Continue/iterate on an existing analysis instead of starting fresh
Workflow Steps
- Fetch - Use
WebFetchto retrieve source content - Metadata - Extract title, author, date, type, generate source-id
- Analysis - Perform 3-stage analysis (see methodology)
- Neutral Analyst Prose Pass - Clean up analyst-authored prose without changing source content, quotes, claim IDs, evidence levels, or credences
- Extract - Format claims as YAML (see methodology)
- Register - Add source and claims to database
- Audit Log - Append in-document Analysis Log + register
analysis_logsrow - Validate - Run integrity checks
- README - Update data project analysis index
- Report - Generate summary
The neutral prose pass applies to the analysis voice, not the content being analyzed. Do not remove direct quotes, source wording, titles, quoted slogans, or examples in persuasion/rhetoric analysis; label those as source language instead of adopting them as the analyst's framing.
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 · 121 lines · 16 tokens per session scan A 9aa761e84b01
check is a command published in the GitHub repository lhl/realitycheck (44 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 1,136 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 commands, from other repositories
awesome-chatgpt
Search awesome-ChatGPT-repositories for open-source GitHub repositories related to ChatGPT and LLMs.
modernize-transform
Transform one legacy module to the target stack — idiomatic rewrite with behavior-equivalence tests.
pr
Handle the full workflow from current branch state to an open, CI-monitored pull request.
bug-check
Run automated tests and build checks first, then agent code review. For each bug found, propose or document a regression test.
requirement-review
A command that has several specialized agents review a requirements document and produce a revised version through a controlled workflow.
hep-local.body
A local workforce command that searches agents registered on this machine and prepares a selected group for a task.