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/extract)<a href="https://agentmods.dev/commands/lhl/realitycheck/extract"><img src="https://agentmods.dev/badge/commands/lhl/realitycheck/extract/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/extract"><img src="https://agentmods.dev/badge/commands/lhl/realitycheck/extract.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.00012 | $0.00587 |
| Opus 5.5 | $0.00005 | $0.00235 |
| Sonnet 5.5 | $0.00002 | $0.00117 |
| Haiku 4.5 | $0.00001 | $0.00059 |
Grade A, and why
extract 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:extract - Claim Extraction
Quick claim extraction from a source without full 3-stage analysis.
Usage
/reality:extract <source>
Arguments
source: URL, file path, or pasted text to extract claims from
Process
- Parse the source content
- Identify extractable claims
- For each claim:
- Assign claim ID:
[DOMAIN]-[YYYY]-[NNN] - Determine type:
[F]/[T]/[H]/[P]/[A]/[C]/[S]/[X] - Rate evidence level (E1-E6)
- Assign credence (0.0-1.0)
- Note operationalization, assumptions, falsifiers
- Assign claim ID:
Registering Claims
After extraction, register claims using the CLI:
# Via shell wrapper
"${CLAUDE_PLUGIN_ROOT}/scripts/run-db.sh" claim add \
--id "DOMAIN-YYYY-NNN" \
--text "Claim text" \
--type "[F]" \
--domain "TECH" \
--evidence-level "E3" \
--credence 0.7 \
--source-ids "source-id"
# Or directly
uv run python scripts/db.py claim add [OPTIONS]
See /reality:check for fully automated analysis + registration workflow.
Claim Types
| Type | Symbol | Definition |
|---|---|---|
| Fact | [F] |
Empirically verified, consensus reality |
| Theory | [T] |
Coherent explanatory framework with support |
| Hypothesis | [H] |
Testable proposition, awaiting evidence |
| Prediction | [P] |
Future-oriented claim with conditions |
| Assumption | [A] |
Unstated premise underlying other claims |
| Counterfactual | [C] |
Alternative scenario for comparison |
| Speculation | [S] |
Untestable or unfalsifiable claim |
| Contradiction | [X] |
Identified logical inconsistency |
Template
Uses methodology/templates/claim-extraction.md
Examples
/reality:extract https://arxiv.org/abs/2301.xxxxx
/reality:extract "AI will automate 50% of jobs by 2030"
Related Commands
/reality:check- Full automated analysis workflow/reality:analyze- Full 3-stage analysis/reality:search- Semantic search/reality:stats- Database statistics
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 · 81 lines · 12 tokens per session scan A 2a87729e0455
extract is a command published in the GitHub repository lhl/realitycheck (44 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 12 tokens to every session and 587 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
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.